Repository navigation
[pkg] fix npm provenance repository metadata - #16
Merged
Merged
Conversation
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.
Summary
expo/agent-cli-detectorlocationRoot cause
The repository moved from
davidmokos/detect-agenttoexpo/agent-cli-detector, butpackage.jsonstill contained the old URL. npm trusted publishing rejected the 0.1.5 provenance because the package metadata did not match the GitHub Actions source repository.Impact
The corrected metadata allows npm to verify the Sigstore provenance bundle for 0.1.5. README links now point directly to the current repository instead of relying on GitHub redirects.
Validation
npm test(15 tests passed)npm pack --dry-run --json