ci: add NPM_TOKEN env var for semantic-release npm publish#235
Closed
ci: add NPM_TOKEN env var for semantic-release npm publish#235
Conversation
@semantic-release/npm requires NPM_TOKEN to authenticate with the npm registry. Without it verifyConditions fails with ENONPMTOKEN. Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
Author
|
Superseded by #236 — upgrading @semantic-release/npm to v13.1.x which supports OIDC natively, removing the need for NPM_TOKEN. |
jairo-bc
force-pushed
the
ci/fix-release-workflow
branch
from
16ba01f to
2beaa20
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.
What/Why?
@semantic-release/npmrequiresNPM_TOKENto authenticate with the npm registry duringverifyConditions. The release workflow was failing withENONPMTOKENbecause the token was previously set via a manual.npmrcstep that was removed — this restores it properly as an env var.Rollout/Rollback
CI/CD configuration change only. Rollback by reverting this PR.
Testing
Verify the next merge to
mastercompletes the release workflow withoutENONPMTOKEN.Note
Low Risk
DevDependency-only version bump; main risk is subtle CI/release behavior changes during npm publish.
Overview
Updates the release toolchain by bumping
@semantic-release/npmfrom^12.0.2to^13.1.5inpackage.jsonto keep semantic-release npm publishing dependencies current.Written by Cursor Bugbot for commit 2beaa20. This will update automatically on new commits. Configure here.