Fix npm publish: remove registry-url to avoid conflict with OIDC trusted publishing#29
Merged
Fix npm publish: remove registry-url to avoid conflict with OIDC trusted publishing#29
Conversation
OIDC trusted publishing requires npm account configuration that isn't set up, causing a 404 on publish. Switch to explicit NPM_TOKEN secret and drop --provenance.
When setup-node sets registry-url, it writes an .npmrc expecting NODE_AUTH_TOKEN. This conflicts with OIDC trusted publishing. Removing registry-url lets npm --provenance use OIDC auth cleanly.
andeplane
changed the title
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.
Problem
npm publish --provenancewas failing with404 Not Found. The trusted publisher is already configured on the npm account, butactions/setup-nodewithregistry-urlwrites an.npmrcthat expects aNODE_AUTH_TOKEN. This conflicts with OIDC auth — npm ends up confused about which auth method to use.Fix
registry-urlfrom thesetup-nodestep (not needed for OIDC publishing)id-token: writepermission and--provenanceflagNODE_AUTH_TOKENneededTest plan
package.json→ workflow should publish successfully via OIDC🤖 Generated with Claude Code