chore: upgrade Node to 24#422
Open
Davydhh wants to merge 2 commits into
Open
Conversation
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
Bumps the pinned Node version from 22.18.0 → 24.18.0 (current Active LTS). Release CI reads
.node-version, so this moves builds onto the newer LTS line and aligns the runtime with@types/node(already^24), which had drifted amajor ahead of the Node 22 pin.
Changes
.node-version:22.18.0→24.18.0That's the whole change.
@types/node ^24.12.0already matches, and pnpm stays pinned viapackageManagerinpackage.json, so nothing else needs touching.Compatibility
The toolchain supports Node 24 (per
engines):^20.19 || >=22.12^20 || ^22 || >=24>=14.17Node 24's breaking changes (OpenSSL 3.5, stricter
AbortSignal, etc.) are runtime/crypto concerns owned by the Rust backend — Node here is only the frontend build/test toolchain, so the exposure is limited to Vite/Vitest.Testing
On Node 24.18.0:
pnpm install,pnpm build, and the full Vitest suite (2713 tests) all pass.