chore(ci): upgrade Node 22 -> 24 across all workflows#3045
Merged
Conversation
Standardize CI on Node 24 (active LTS), matching facebook/lexical. Node 24 bundles npm 11.x, which natively supports OIDC trusted publishing (npm >= 11.5.1) — Node 22 shipped npm 10.x, which is why the first OIDC publish 404'd. Bumps node-version 22 -> 24 in all 9 workflows (17 occurrences): ci, deploy, lint, cli-smoke-test, codemod-verify, vercel-preview, vibe-screenshots, redeploy-preview. No engines/.nvmrc pin exists, so workflows are the only source of truth. Independent of the #3044 npm-upgrade fix (which stays as belt-and-suspenders).
zurfyx
requested review from
cixzhang,
ejhammond,
imdreamrunner,
josephfarina,
marie-lucas,
nynexman4464 and
thedjpetersen
as code owners
meta-cla
Bot
added
the
CLA Signed
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
🚀 Vercel Preview Deployment
|
Contributor
PR Analysis Report📚 Storybook PreviewView Storybook for this PR 🧪 Sandbox PreviewView Sandbox for this PR No new or modified components detected. Bundle Size Summary
Accessibility AuditStatus: No accessibility violations detected. Generated by PR Enrichment workflow | Storybook | Sandbox | View full report |
cixzhang
approved these changes
Jun 24, 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.
Summary
Standardizes CI on Node 24 (active LTS), matching facebook/lexical. Bumps
node-version: 22 -> 24in all 9 workflows (17 occurrences):ci,deploy,lint,cli-smoke-test,codemod-verify,vercel-preview,vibe-screenshots,redeploy-preview. Noengines/.nvmrcpin exists, so workflows were the only source of truth.Why
Node 24 bundles npm 11.x, which natively supports OIDC trusted publishing (requires npm ≥ 11.5.1). Node 22 ships npm 10.x — the reason the first OIDC publish returned a misleading
404. This is also why publishing works on Lexical (node 24) and didn't here (node 22).Independent of #3044 (the explicit
npm install -g npm@latestfix), which stays in place as belt-and-suspenders.Validation ("break nothing")
node:24linux container (install + test + build) — results in a comment.Do not merge until all CI checks are green on Node 24.