Skip to content

Update nodejs from v22.11.0 to v24.4.1 #9275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
liranmauda merged 1 commit into from
Nov 11, 2025
Merged

Update nodejs from v22.11.0 to v24.4.1 #9275

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .nvmrc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
22.11.0
24.4.1
Copy link

@coderabbitai coderabbitai bot Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify compatibility and CI alignment for the two-major-version bump.

The update jumps from v22 to v24, which is a significant version bump that may introduce breaking changes. Before merging, please confirm:

  1. Compatibility: Are there any breaking changes or API deprecations between Node.js v22 and v24 that affect this project?
  2. LTS Status: Is v24.4.1 a stable/LTS release or will it require frequent updates?
  3. CI Alignment: Check if GitHub Actions workflows (.github/workflows/) or other CI configuration files also hardcode Node.js versions and need updating for consistency.
  4. Dependencies: Verify that package.json (if present) has compatible engines field or similar constraints.

🏁 Script executed:

#!/bin/bash
# Description: Check for hardcoded Node.js versions in CI config files and package.json

# Search for hardcoded Node.js versions in GitHub Actions workflows
echo "=== Checking GitHub Actions workflows for Node.js versions ==="
fd -e yml -e yaml '.github/workflows' 2>/dev/null | xargs grep -l 'node-version\|node_version' 2>/dev/null || echo "No workflow files found or no matches"

# Check package.json for engines field
echo -e "\n=== Checking package.json for engines field ==="
if [ -f "package.json" ]; then
  jq '.engines' package.json 2>/dev/null || echo "No engines field in package.json"
else
  echo "package.json not found"
fi

# Search for any other version references in CI or config files
echo -e "\n=== Searching for other Node.js version references ==="
rg -i 'node.*22\.|node.*v22|nodejs.*22' '.github/' -A2 -B2 2>/dev/null || echo "No v22 references found in .github/"

Length of output: 246

🌐 Web query:

What are the breaking changes and LTS status of Node.js v24 compared to v22?

💡 Result:

Short answer

  • Breaking changes: see migration highlights — dropped some prebuilt platforms (32-bit Windows x86 removed in v23; 32-bit Linux armv7 removed in v24), OpenSSL upgraded to 3.5 with default security level 2 (short keys/RC4 disallowed), stricter runtime/argument validation (fetch(), AbortSignal, stream/pipe error behavior, Buffer/path fixes), V8 bump (native addons need rebuild/possible API changes — V8 13.6), C/C++ toolchain requirements (GCC ≥12.2, Xcode ≥16.1), and several deprecations/removals with available codemods (fs constants, REPL/REPL APIs, some legacy TLS/fs APIs). Test native addons and code paths that touch crypto, streams, Buffer, and platform-specific binaries when migrating. [1]

  • LTS status and dates: Node.js v24 (codename “Krypton”) entered Active LTS on 2025-10-28 and is in LTS with support through end of April 2028. Node.js v22 (codename “Jod”) is in Maintenance LTS (post‑Active) and its planned End‑of‑Life is April 30, 2027. [2][1]

Sources

  1. Node.js migration guide: “v22 to v24” (breaking changes, OpenSSL, platforms, addons, codemods). [1]
  2. Node.js releases / schedule (v24 LTS date and v22 status/EoL). [2]

Confirm testing of breaking changes before merging the two-major-version upgrade.

The upgrade from v22 to v24 is a significant jump with documented breaking changes that require verification. v24 (codename "Krypton") entered Active LTS on 2025-10-28 with support through April 2028, making it a supported LTS release. However, breaking changes include dropped prebuilt platforms (32-bit Windows x86 removed in v23; 32-bit Linux armv7 removed in v24), OpenSSL upgraded to 3.5 with default security level 2, stricter runtime/argument validation, and V8 bump to 13.6.

Before merging, ensure:

  • Test native addons and crypto/stream operations: Test native addons and code paths that touch crypto, streams, Buffer, and platform-specific binaries when migrating.
  • Verify platform support: Confirm the project does not require 32-bit Windows or Linux armv7 support.
  • CI alignment: No CI workflow updates needed (no v22 hardcoding detected in GitHub Actions workflows).
🤖 Prompt for AI Agents 
In .nvmrc around line 1 (currently "24.4.1"), you upgraded Node from v22 to v24
but did not verify breaking changes; before merging, run and document targeted
compatibility tests for native addons and any code touching crypto, streams,
Buffer, and platform-specific binaries (exercise CI, local builds, and
integration tests), confirm the project does not require dropped platforms
(32-bit Windows x86 or Linux armv7), update CI workflows if any hardcoded Node
versions are found or to add runners that match supported platforms, and add a
short PR note/changelog entry listing the verification steps and any CI changes
so reviewers can confirm the checks were completed.