fix(release): drop registry-url so npm performs the OIDC exchange - #15
Merged
Conversation
setup-node's registry-url writes an .npmrc auth line with a placeholder NODE_AUTH_TOKEN; npm 11.18 then skips trusted publishing and the PUT fails E404. No token config -> npm negotiates OIDC (default registry).
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.
First v1.5.0 publish attempts failed E404: setup-node's registry-url writes a placeholder-auth .npmrc, so npm skips the trusted-publisher OIDC exchange (no 'trusted publisher' notice in the logs) and PUTs with garbage credentials. Removing registry-url lets npm >=11.5.1 negotiate OIDC against its default registry. After merge: recreate the v1.5.0 tag at main to re-trigger the publish (nothing was published; same version).
🤖 Generated with Claude Code