chore(deps): upgrade @semantic-release/npm to v10 for OIDC trusted publishing - #538
Merged
Conversation
…blishing support @semantic-release/npm@9 does not support npm trusted publisher OIDC authentication, causing 'No npm token specified' errors (#537). v10 adds native OIDC support, allowing semantic-release to use the GitHub Actions OIDC token directly without NPM_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.
Problem
The automated release workflow (Issue #537) is failing with "No npm token specified" error after migrating to NPM trusted publisher OIDC flow.
Root Cause
@semantic-release/npm@9.0.1does not support npm trusted publisher OIDC authentication. It only checks forNPM_TOKENenv var or auth config in.npmrc. With the OIDC migration removingNPM_TOKENandregistry-urlfromsetup-node, there's no authentication available for semantic-release.Fix
Upgraded
@semantic-release/npmfrom^9.0.1to^10.0.0.v10 adds native OIDC support, allowing semantic-release to use the GitHub Actions OIDC token directly via
id-token: writepermission — noNPM_TOKENorregistry-urlneeded.Changes
package.json:"@semantic-release/npm": "^9.0.1"→"^10.0.0"Related
Fixes #537 (follow-up to #535)