fix: point package.json URLs at ledger-casper-js (fixes OIDC provenance 422)#4
Merged
Conversation
…ce 422) repository.url / homepage / bugs pointed at github.com/Zondax/ledger-casper (the C app repo). On `npm publish --provenance`, npm validates that repository.url matches the repo that generated the provenance (ledger-casper-js) and rejected the mismatch with E422.
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
Correct
repository.url,homepage, andbugs.urlinpackage.jsonfromZondax/ledger-casper→Zondax/ledger-casper-js.Why
Zondax/ledger-casperis the C app repo. With the@v7publish workflow now reaching the real publish step,npm publish --provenancevalidates thatrepository.urlmatches the repo that generated the sigstore provenance (ledger-casper-js), and rejected the mismatch:After merge
Re-cut the
v2.6.4release (delete + recreate the tag onmain, or bump tov2.6.5) so the release runs from a commit containing this fix.