fix(release): upgrade npm for OIDC trusted publishing auth#57
Merged
Conversation
npm 10.x (Node 22) supports provenance signing via OIDC but not publish authentication. The registry OIDC auth exchange requires npm 11.5.1+. Upgrading npm in CI enables the full trusted publishing flow without an NPM_TOKEN.
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
Follow-up to #56. The
.npmrcremoval andregistry-urladdition were necessary but insufficient — npm 10.x (Node 22) does not support OIDC publish authentication, only provenance signing.npm install -g npm@lateststep to upgrade to npm 11.5.1+ which supports the full OIDC trusted publishing flowRoot Cause
npm 10.x can sign provenance via OIDC (Sigstore) but cannot authenticate the
PUTrequest via OIDC. The registry returnsE404because the publish is effectively unauthenticated. npm 11.5.1+ adds native OIDC auth exchange with the npm registry.Test plan
npm --versionin CI logs shows 11.x+