Repository navigation
Drop setup-node registry-url so npm uses OIDC - #3
Merged
Merged
Conversation
With registry-url set, setup-node writes an .npmrc that reads a placeholder NODE_AUTH_TOKEN, and npm publish authenticates with that placeholder instead of exchanging the GitHub OIDC token. The v2.0.0 release run failed with 404 and no provenance for that reason.
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
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.
The retagged v2.0.0 release run (38189878074) failed with 404 on publish. Its log shows
NODE_AUTH_TOKEN: XXXXX-XXXXX-XXXXX-XXXXX, the placeholder setup-node writes whenregistry-urlis set, and the publish notice has no provenance line, so npm never attempted the OIDC exchange. Removingregistry-urlstops the placeholder .npmrc from being written; npm 12 on the runner then uses trusted publishing on its own. No other change.