fix(release): pin npm to 11.x so OIDC publish works on Node 20#327
Merged
Conversation
npm@latest rolled to 12.x, which requires Node >=22.22.2 and fails with EBADENGINE on our Node 20 runner. The 'Upgrade npm' step has failed on every push to main since npm@12 shipped (~07-09), skipping the changesets action, so no Version Packages PR opened and several merged changesets went unreleased. Pin to npm@11 (>=11.5.1, still supports Node 20) — that's all OIDC needs.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
brtkx
approved these changes
Jul 15, 2026
OmarBasem
pushed a commit
that referenced
this pull request
Jul 15, 2026
OmarBasem
pushed a commit
that referenced
this pull request
Jul 16, 2026
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
2 participants
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.
Why the Version Packages PR stopped opening
npm@latestrolled to 12.x, which requires Node>=22.22.2. The release workflow pins Node 20, so theUpgrade npm for OIDC publishingstep (npm install -g npm@latest) now fails withEBADENGINE:That step failing skips
Create Version PR or publish— so since ~07-09 every merge to main has silently failed to open/update the Version PR. Changesets from #299/#300/#304/#305/#306 piled up on main, unreleased.Fix
Pin to
npm@11(≥ 11.5.1, which is all OIDC Trusted Publishing needs, and still supports Node 20). Stops chasinglatestinto engine breaks.After merge
The (fixed) release run will process the pending changesets and open a Version Packages PR bumping
@zerodev/react-uiand@zerodev/wallet-react-ui. Merging that publishes them.Follow-up (separate): Node 20 is deprecated on GH runners — worth bumping the workflows to Node 22 later, but that's not needed to unblock this.