fix: add repository field to package.json for npm provenance#176
Merged
Conversation
npm OIDC trusted publishing generates provenance attestations that require package.json repository.url to match the source repository. Without this field, npm rejects the publish with E422: 'repository.url is "", expected to match https://github.com/enboxorg/gitd'
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
Fixes the npm OIDC trusted publishing failure from #175. The OIDC authentication now works, but npm rejects the publish with E422:
npm's provenance verification requires
package.jsonto have arepositoryfield matching the source repo. This was missing.Change: Add
repositoryfield topackage.jsonpointing tohttps://github.com/enboxorg/gitd.Build, test, and lint all pass.