Fix OIDC auth for npm Trusted Publishers#17
Merged
sdserranog merged 2 commits intomainfrom Mar 5, 2026
Merged
Conversation
actions/setup-node with registry-url creates .npmrc with
//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}. This empty
placeholder prevents npm from using the OIDC exchange for Trusted
Publishers. Deleting the _authToken config after setup lets npm
fall through to OIDC-based authentication.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
sdserranog
force-pushed
the
sdserranog/fix-npm-trusted-pub
branch
from
bdfdbf9 to
6afbc37
Compare
Node 22 ships with npm v10.x which does not support OIDC-based trusted publishing. OIDC support was added in npm v11.5.1. Adding `npm install -g npm@latest` before publish ensures the OIDC token exchange with npm works correctly. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
registry-urlinactions/setup-node(needed for registry config)_authTokenplaceholder from.npmrcafter setup so npm uses OIDC exchange instead of the empty tokenContext
registry-url: npm getsENEEDAUTH(no auth at all)registry-url+${NODE_AUTH_TOKEN}placeholder: npm sends empty token, getsE404registry-url+_authTokendeleted: npm should fall through to OIDC-based Trusted Publisher authTest plan
npm view @arcadeai/create-agent versionreturns0.2.3🤖 Generated with Claude Code