ci: use setup-node v6 so npm OIDC trusted publishing works - #37
Merged
Conversation
setup-node v4 writes a placeholder auth token to .npmrc, which npm uses instead of OIDC and the registry rejects (masked 404). v6 is OIDC-aware; matches npm's documented trusted-publishing setup (node 24, no token).
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.
Second fix for the 0.6.1 publish. The previous attempt got past
ENEEDAUTH(npm 11.16, registry-url set) but hitE404—actions/setup-node@v4writes a placeholder_authTokento .npmrc (visible as thealways-authwarning +NODE_AUTH_TOKEN: XXXXX-...), so npm used that bogus token instead of OIDC and the registry rejected it.setup-node@v6is OIDC-aware and matches npm's documented recipe (node 24, registry-url, no token). After merge I'll dispatch the workflow again to publish 0.6.1.