fix: repository.url casing for npm provenance validation - #6
Merged
Conversation
…ation npm provenance verification compares package.json repository.url to the GitHub Actions build source case-sensitively; the lowercase org slug failed the 0.2.1 publish 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
2 participants
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.
The trusted-publisher publish of 0.2.1 failed E422: provenance validation compares
repository.urlto the build source case-sensitively, and package.json had the lowercasespeechify-aiorg slug:OIDC itself worked (statement signed + logged to Sigstore) — this casing fix is the last blocker. Merging this as
fix:makes release-please cut 0.2.2, whose publish should go through fully automated. (0.2.1 stays tagged but unpublished — its package.json is frozen with the bad casing, so republish isn't possible; skipping to 0.2.2 is the clean path.)