Fix npm OIDC trusted publishing and upgrade Node to v25#223
Merged
Conversation
|
The release workflow was failing with E404 when publishing to npm using OIDC trusted publishing. Root causes: - changesets/action@v1 sets NODE_AUTH_TOKEN to a raw GitHub OIDC JWT, which npm cannot use directly as an auth token - setup-node's registry-url creates a conflicting _authToken in .npmrc - npm >= 11.5.1 is required for OIDC trusted publishing (handles the OIDC token exchange internally) Changes: - Upgrade .nvmrc from Node 18 to Node 25 (ships with npm >= 11.5.1) - Remove registry-url from setup-node to avoid auth conflicts - Skip changesets/action publish, handle it in a separate step - Add workflow_dispatch trigger for manual runs - Let npm CLI handle OIDC exchange natively via --provenance Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
30fa135 to
3cb2717
Compare
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
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 release workflow was failing with E404 when publishing to npm using OIDC trusted publishing. Root causes:
Changes: