Repository navigation
Fix repository/homepage URLs to match this repo (needed for npm provenance) - #2
Merged
Merged
Conversation
…or npm provenance)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
package.json
repository.urlandhomepageand the node's codex docs links pointed to a non-existent repo (batchdata-n8n-node). npm provenance (required for n8n community nodes) verifies thatrepository.urlmatches the GitHub repository that runs the publish workflow, so a mismatch would make the publish fail. Metadata-only change; no code changes.