fix: correct npm repository URL for OIDC provenance validation #108
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 v0.14.6 release failure. npm's OIDC provenance check requires
repository.urlin the publishedpackage.jsonto match the actual GitHub repo URL from the provenance attestation.The error
Fix
Test plan
Note
Low Risk
Single-field change to release metadata; affects npm publish validation but not runtime code paths.
Overview
Fixes npm release metadata by updating the
npmsconfig in.goreleaser.yamlso the published packagerepositoryURL points tohttps://github.com/kernel/cliinstead of the org root, aligning with OIDC/sigstore provenance expectations.Written by Cursor Bugbot for commit 3eb197d. This will update automatically on new commits. Configure here.