ci: give yarn an empty NODE_AUTH_TOKEN on publish - #140
Merged
Conversation
setup-node's registry-url writes an .npmrc containing
${NODE_AUTH_TOKEN}. Publishing goes through OIDC trusted publishing, so
no such token exists, and yarn v1 aborts rather than expanding an env
var that is absent: "Failed to replace env in config".
Defining it as empty is enough for yarn's expansion to succeed. npm
reads the same empty value as no auth and falls through to trusted
publishing, which is what already happens today.
Co-Authored-By: Claude Opus 5 <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.
setup-node's registry-url writes an .npmrc containing ${NODE_AUTH_TOKEN}. Publishing goes through OIDC trusted publishing, so no such token exists, and yarn v1 aborts rather than expanding an env var that is absent: "Failed to replace env in config".
Defining it as empty is enough for yarn's expansion to succeed. npm reads the same empty value as no auth and falls through to trusted publishing, which is what already happens today.