bump to node 24

[alexcos20]

Changes proposed in this PR:

• bump node to v24

Summary by CodeRabbit

• Chores
  • Upgraded the required Node.js runtime to version 24.
  • Updated development, testing, and deployment environments to use Node.js 24.
  • Updated runtime documentation and setup requirements to reflect the new version.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e1f02a0d-0467-41f1-b2da-bf4cfe63934b

📥 Commits

Reviewing files that changed from the base of the PR and between d52abe7 and 8aea706.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (5)

• .github/workflows/ci.yml
• .nvmrc
• CLAUDE.md
• Dockerfile
• package.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The project now targets Node.js 24.19.0 across package engine requirements, local development, Docker images, CI jobs, and runtime documentation.

Changes

Node.js 24 runtime upgrade

Layer / File(s)	Summary
Runtime baseline .nvmrc, Dockerfile, package.json	The minimum package engine version is now >=24. Local development and both Docker stages use Node.js 24.19.0 with updated image digests.
CI and documentation alignment .github/workflows/ci.yml, CLAUDE.md	Lint, build, unit-test, integration-test, and system-test jobs now use Node.js 24.19.0. Runtime and Docker documentation now reference Node.js 24.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 8aea7

This Node.js version bump has no actionable merge-blocking risk in the supplied evidence and is merge-ready after normal checks and review.

Suggested reviewers: giurgiur99, andreip136

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the primary change: upgrading the project to Node.js 24.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (5 skipped: 5 unsupported.)
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch deps/node_v24

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[alexcos20]

/run-security-scan

[alexcos20]

AI automated code review (Gemini 3).

Overall risk: low

Summary:
The PR successfully updates the Node.js runtime from 22.23.1 to 24.19.0 across CI workflows, Dockerfile, NVM config, and package metadata. A few minor improvements are recommended to maintain consistency and POSIX compliance.

Comments:
• [INFO][style] The trailing newline was accidentally removed in this update. POSIX standards dictate that text files should end with a newline character to prevent potential parsing issues with certain CLI tools (like cat or some shell scripts). Please restore the trailing newline.

-24.19.0
\ No newline at end of file
+24.19.0

• [WARNING][bug] Previously, the engine requirement was specific (>=22.13.0). Changing it to the broader >=24 allows any Node 24.x version (e.g., 24.0.0). Since .nvmrc and the Dockerfile explicitly pin 24.19.0, it is safer to enforce >=24.19.0 here. This ensures developers don't encounter unexpected bugs by using an earlier minor version of Node 24 that might lack necessary features or security patches.

   "engines": {
-    "node": ">=24"
+    "node": ">=24.19.0"
   },

• [INFO][style] If you update the package.json engines to >=24.19.0 as suggested, ensure you also update this documentation line to maintain consistency.

-  matching the Dockerfile and CI; `package.json` `engines` requires `>=24`, so Node 22 is
+  matching the Dockerfile and CI; `package.json` `engines` requires `>=24.19.0`, so Node 22 is