Repository navigation
fix: @W-24754518 add repository field to package.json for npm provenance - #35
Merged
Merged
Conversation
npm trusted publishing rejected 1.0.3 (E422) because package.json had no repository.url to match the GitHub provenance statement. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
What
Add
repository,homepage, andbugstopackage.json(same format as plugin-api).Why
The first trusted-publishing release (1.0.3, after #34) failed in the publish workflow:
OIDC auth and provenance signing succeeded; npm rejected the package only because
package.jsonhad norepositoryfield. Merging this (fix:) triggers 1.0.4, which should publish with provenance.Testing
yarn build/yarn test✅ (pre-push hook)npm pkg get repository→"salesforcecli/plugin-data-setup-transfer"🤖 Generated with Claude Code