chore: update Node.js to 24.21.0 - #1731
Merged
Merged
Conversation
Move to the latest release of the Node.js 24 LTS line (Krypton). - .nvmrc (read by CI) and engines.node in package.json (read by Vercel) - matching engines entry in package-lock.json - README prerequisites
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Bugbot needs on-demand usage enabledBugbot uses usage-based billing for this team and requires on-demand usage to be enabled. A team admin can enable on-demand usage in the Cursor dashboard. |
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
A published AI-agent tutorial still references Node.js 24.18.0.
Review effort: Lite
Findings: 1
Open (1)
What changed in this PR
Updates the Node.js baseline from 24.18.0 to 24.21.0 across project configuration and documentation.
Changes:
- Pins Node.js 24.21.0 in development and package metadata.
- Synchronizes the lockfile engine entry.
- Updates the README prerequisite.
| File | Description |
|---|---|
README.mdx |
Documents Node.js 24.21.0. |
package.json |
Updates the Node.js engine requirement. |
package-lock.json |
Synchronizes root engine metadata. |
.nvmrc |
Pins Node.js 24.21.0. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
jimmeilin
approved these changes
Sep 30, 2026
This branch was successfully deployed
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
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
Updates Node.js from 24.18.0 to 24.21.0, the latest release of the Node.js 24 LTS line (Krypton), published 2026-09-07.
The version is pinned in four places, all updated together:
.nvmrc, which the CI workflows read through the shared actionsengines.nodeinpackage.json, which Vercel readsenginesentry inpackage-lock.json(no other lockfile changes)README.mdxNode.js 26 is out of scope. It's still the "Current" release line rather than LTS, and moving to it is a major upgrade.
Verification
Run locally under Node.js 24.21.0 with its bundled npm 11.19.0:
engines.noderange (1,293 of them) accepts 24.21.0. The only exception is the optional 32-bit Windowssharpbinary, which already rejects 24.18.0 and isn't installed on other platforms.npm ci,npm run lint,npm run typecheck,npm run agent-docs:test,npm run buildandnpm run agent-docs:checkall pass, with no engine warnings. So does CI's build path:npm ci --only=productionfollowed bynpm run build.mainbuild made with Node.js 24.18.0. That covers all 2,054 files, including every JS and CSS bundle and the generated social-card images, with both full and production-only installs.