fix: enable npm trusted publishing in release workflow#6
Merged
Conversation
…hing setup-node with registry-url creates .npmrc with an empty NODE_AUTH_TOKEN, which prevents npm from using OIDC for authentication. 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-urlfromsetup-nodein the release workflowsetup-nodewithregistry-urlcreates~/.npmrcwith_authToken=${NODE_AUTH_TOKEN}, and since no token is set, npm uses the empty string as auth — failing with "Access token expired or revoked" before trying OIDC.npmrcentry, npm will use OIDC-based trusted publishing for authenticationTest plan
react-http-renderer@0.2.0to npm successfully🤖 Generated with Claude Code