ci: fix public npm publish to use OIDC trusted publishing - #6
Merged
Conversation
Drop setup-node registry-url: its empty _authToken .npmrc shadowed OIDC, causing a 404 on publish. Default registry (npmjs.org) + id-token now use OIDC. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
The first
publish-publicrun failed atnpm publishwithE404 PUT /reply-cli … you do not have permission.Root cause:
actions/setup-nodewithregistry-url:writes an.npmrcline//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}. We publish tokenlessly via OIDC trusted publishing, soNODE_AUTH_TOKENis empty — npm used that empty token instead of OIDC (no OIDC attempt in the logs) and the registry returned 404. Provenance still signed because that's a separate OIDC path.Fix: drop
registry-url(default registry is npmjs.org anyway oncepublishConfigis removed), so no token.npmrcshadows OIDC. Also echonpm --versionto confirm >= 11.5.1 at runtime.Nothing was published, so
v0.3.0is still free to retry after this merges.Ref: REPLY-51236