fix: add repository field so npm provenance passes#51
Merged
Conversation
npm publish with provenance (sigstore) fails with E422 when package.json has no repository.url — it must match the GitHub repo recorded in the provenance bundle. Adds repository/homepage/bugs to the root package and both adapters.
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
1 participant
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.
Summary
E422on all three packages:package.jsonfiles had arepositoryfield. WithNPM_CONFIG_PROVENANCE=true, npm requires it and must match the signed provenance.repository,homepage, andbugsto the root package and both adapters (each adapter setsdirectoryfor a monorepo-aware link on npmjs.com).Test plan
changeset publish