fix(ISSUE-16): upgrade npm to latest for OIDC registry auth#22
Merged
Conversation
npm 10.9.8 (ships with Node 22) uses OIDC for Sigstore provenance but does not exchange the OIDC token for npm registry authentication. npm 11+ handles both. Upgrade npm before publish.
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.
Problem
npm 10.9.8 (ships with Node 22) performs OIDC token exchange for Sigstore provenance (works), but does NOT exchange the token for npm registry authentication. The registry PUT receives no credentials and returns
404(scoped packages are invisible without auth).Fix
Upgrade npm to latest (11.x) before publishing. npm 11+ handles both Sigstore provenance and OIDC registry auth automatically when
NODE_AUTH_TOKENis not set.