ci: drop registry-url so npm publish reaches the OIDC exchange - #3
Merged
Conversation
setup-node's registry-url writes an .npmrc with an _authToken line and exports a placeholder NODE_AUTH_TOKEN when none is provided. npm then presents that placeholder as a real token instead of attempting the trusted-publishing OIDC exchange, and the registry masks the rejection as E404 — proven live on the sibling headerless repository's first automated publish. With no auth configured at all, npm falls through to OIDC.
firejune
enabled auto-merge (squash)
August 23, 2026 11:17
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.
Same fix as firejune/headerless#13, where the first automated publish failed with
npm error 404:setup-node'sregistry-urlwrites an.npmrcwith an_authTokenline and exports the placeholderNODE_AUTH_TOKEN: XXXXX-XXXXX-XXXXX-XXXXXwhen none is provided, so npm presents that placeholder as a real token instead of attempting the trusted-publishing OIDC exchange, and the registry masks the auth rejection as E404. With no auth configured, npm falls through to OIDC. The default registry is npmjs anyway, so nothing else changes.