fix(release): use exec plugin for npm publish to bypass token validation#391
Merged
Conversation
@semantic-release/npm validates tokens in verifyConditions before publish, but setup-node OIDC auth only works at npm publish time. Replace with @semantic-release/exec to call npm publish directly.
mohnoor94
force-pushed
the
fix-release-npm-publish
branch
from
e17921a to
033b1b2
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
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/npmwith@semantic-release/execfor npm publishing@semantic-release/npmvalidates tokens inverifyConditionsbefore publish, butsetup-node@v6OIDC auth only works at actualnpm publishtime@semantic-release/execcallsnpm publish --access publicdirectly, letting setup-node's OIDC handle authFollows up on PR #390 which added
setup-node@v6withregistry-url.🤖 Generated with Claude Code