ci: enable OIDC trusted publishing (strip setup-node empty _authToken) - #7
Merged
Merged
Conversation
Restore registry-url (required for OIDC) and delete the empty _authToken line setup-node writes; it was shadowing the OIDC exchange (ENEEDAUTH/404). Root cause: actions/setup-node#1551. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Root cause (confirmed via actions/setup-node#1551 + npm docs):
setup-nodewithregistry-urlwrites an empty//registry.npmjs.org/:_authToken=line whenNODE_AUTH_TOKENis unset. npm then treats auth as configured and never initiates the OIDC token exchange, so trusted publishing fails:E404on the PUT (run 1),registry-urlremoved (no registry for OIDC) →ENEEDAUTH(run 2).Fix: keep
registry-url(required for OIDC) and delete the_authTokenline from the.npmrcbefore publishing, so npm falls through to the OIDC exchange (ACTIONS_ID_TOKEN_REQUEST_*→/-/npm/v1/oidc/token/exchange).Also confirmed satisfied: npm 12.0.1 (≥11.5.1), node 22 (≥22.14),
id-token: write,package.jsonrepository.urlmatches the repo, explicit--provenance.Nothing was ever published, so
v0.3.0is still free.Ref: REPLY-51236