ci(publish): switch to npm Trusted Publishing (OIDC) - #6
Merged
Conversation
The granular access token approach failed: npm publish returned 403
("You may not perform that action with these credentials") even with
Bypass 2FA enabled and Read+write scoped to just this package. npm has
removed Classic token creation for this account, and their own direction
is clearly Trusted Publishing (OIDC) now -- no token/secret to store,
leak, or expire.
- node-version bumped 20 -> 22 (Trusted Publishing needs npm CLI >=11.5.1,
which needs Node >=22.14)
- dropped the NODE_AUTH_TOKEN env var / NPM_TOKEN secret entirely; npm CLI
auto-detects the OIDC context from id-token: write (already present)
Requires linking this repo + publish.yml under this package's Settings >
Trusted publishing on npmjs.com before it will work.
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.
Granular access token publish failed with 403 despite Bypass-2FA + Read/write scoping. npm has removed Classic token creation for this account and is pushing Trusted Publishing (OIDC) instead -- no token/secret needed at all.
Requires linking this repo+publish.yml under the package's Settings > Trusted publishing on npmjs.com (user has done this).