ci: upgrade @semantic-release/npm to v13.1 for native OIDC support#36
Merged
Conversation
- Bump @semantic-release/npm from ^12.0.2 to ^13.1.0 (native npm OIDC — no NPM_TOKEN needed) - Remove registry-url from setup-node to prevent NODE_AUTH_TOKEN injection blocking OIDC - Remove manual OIDC curl token exchange step (now handled natively by the plugin) - Add NODE_AUTH_TOKEN: "" in Semantic Release step to explicitly clear any injected value - Add npm install -g npm@latest step to ensure npm >= 11.5.1 - Add provenance: true to publishConfig for npm attestations Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
🎉 This PR is included in version 1.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Summary
@semantic-release/npmfrom^12.0.2→^13.1.0— this version natively handles npm Trusted Publisher OIDC, replacing the brokennpm whoamicheckregistry-urlfromsetup-node— it was injectingNODE_AUTH_TOKENand blocking OIDCnpm install -g npm@latestto ensure npm >= 11.5.1 (required for OIDC exchange)NODE_AUTH_TOKEN: ""explicitly in the release step to clear any injected valueprovenance: truetopublishConfigin package.jsonWhy
The previous approach tried to manually exchange OIDC tokens via curl — that endpoint isn't publicly documented and returned null.
@semantic-release/npmv13.1.0+ handles the OIDC exchange natively using GitHub Actions'id-token: writepermission. No storedNPM_TOKENrequired.References
🤖 Generated with Claude Code