fix: pass NPM_TOKEN to semantic-release in release workflow#1026
fix: pass NPM_TOKEN to semantic-release in release workflow#1026craigcarlyle merged 1 commit intomainfrom
Conversation
The Release step was missing NODE_AUTH_TOKEN, causing npm authentication to fail during semantic-release's verifyConditions phase. Made-with: Cursor
craigcarlyle
requested review from
a team and
rmartins90
and removed request for
a team
craigcarlyle
added
the
👀 Show PR
doistbot
left a comment
doistbot
left a comment
There was a problem hiding this comment.
This PR provides a clear and essential fix to the CI workflow by correctly passing the NPM_TOKEN to semantic-release, successfully restoring the automated release process. The change is straightforward and well-implemented, and no issues were flagged during the review.
## [30.1.1](v30.1.0...v30.1.1) (2026-04-03) ### Bug Fixes * pass NPM_TOKEN to semantic-release in release workflow ([#1026](#1026)) ([cc23af1](cc23af1)) * preserve spacing for loose lists in Prose component ([#1025](#1025)) ([67d6aae](67d6aae)) * revert partial 30.1.1 release to allow clean re-release ([#1027](#1027)) ([64c6447](64c6447))
|
🎉 This PR is included in version 30.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
✅ |
|
@rfgamaral can you double check this please? I thought we used OIDC and removed the npm tokens? 🤔 |
We did, but Reactist was using |
5 participants
Summary
NODE_AUTH_TOKEN, causingsemantic-releaseto fail withEINVALIDNPMTOKENduring theverifyConditionsphase.actions/setup-nodecreates a temporary.npmrcreferencing${NODE_AUTH_TOKEN}, but that env var was never set for the Release step.NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}to the Release step's environment.Test plan
maincommit.Made with Cursor