fix: add repository field so provenance validation passes - #13
Merged
Conversation
npm rejects provenance-signed publishes (E422) when package.json repository.url does not match the repo the OIDC token attests to. This is what failed the v0.1.1 publish after trusted publishing was configured.
Greptile SummaryAdds canonical GitHub repository metadata to the package manifest so npm can validate trusted-publishing provenance.
Confidence Score: 5/5The PR appears safe to merge with no actionable defects identified. The added repository URL matches the project’s canonical remote, and the release workflow publishes from this root manifest without a conflicting metadata source. Important Files Changed
Reviews (1): Last reviewed commit: "fix: add repository field so provenance ..." | Re-trigger Greptile |
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.
npm hard-requires
repository.urlto match the repo attested in the OIDC provenance bundle. Without it, provenance-signed publishes fail:This is the last blocker for CI publishes (failed run). Merging this will make release-please cut v0.1.2, and that release will publish cleanly via trusted publishing.