fix: add repository metadata for npm provenance - #13
Merged
Conversation
Trusted publishing (OIDC) generates a provenance statement and npm rejects the publish (E422) unless package.json `repository.url` matches the source repo. The field was missing, so `repository.url` resolved to "" and provenance verification failed. Add repository, homepage and bugs pointing to Qwant/answer-node. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
What
Add
repository,homepageandbugsfields topackage.json.Why
With OIDC trusted publishing, npm generates a provenance statement and rejects the publish unless
package.jsonrepository.urlmatches the source repo:repositorywas missing entirely, so the value resolved to""and provenance verification failed — the last thing blocking the publish (the tarball built and the provenance was signed; only this validation failed).After merge
The release should finally publish 1.0.0 to npm with provenance.
🤖 Generated with Claude Code