Upgrade to Node.js 24

[kdenhartog]

Summary

• Updates Node.js engine requirement to >=24.11.1 <25.0.0 in package.json
• Updates CI workflows (build.yml, unit-tests.yml) to use Node.js 24
• Updates Dockerfile.ci base image from node:lts-bookworm to node:24-bookworm
• Cleans up package-lock.json with engine metadata

Test plan

• Verify CI builds pass with Node.js 24
• Verify unit tests pass
• Verify integration tests pass with updated Docker image
• Confirm no compatibility issues with dependencies

🤖 Generated with Claude Code

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		High CVE: Serialize JavaScript is Vulnerable to RCE via RegExp.flags and Date.prototype.toISOString() in npm serialize-javascript CVE: GHSA-5c6j-r48x-rmvq Serialize JavaScript is Vulnerable to RCE via RegExp.flags and Date.prototype.toISOString() (HIGH) Affected versions: < 7.0.3 Patched version: 7.0.3 From: package-lock.json → npm/webpack@5.104.1 → npm/serialize-javascript@6.0.2 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/serialize-javascript@6.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Medium CVE: Serialize JavaScript has CPU Exhaustion Denial of Service via crafted array-like objects in npm serialize-javascript CVE: GHSA-qj8w-gfj5-8c6v Serialize JavaScript has CPU Exhaustion Denial of Service via crafted array-like objects (MODERATE) Affected versions: < 7.0.5 Patched version: 7.0.5 From: package-lock.json → npm/webpack@5.104.1 → npm/serialize-javascript@6.0.2 ℹ Read more on: This package | This alert | What is a medium CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known medium severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/serialize-javascript@6.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[mihaiplesa]

Needs a rebase.

[remusao]

Was it necessary to refresh the whole lock?

[kdenhartog]

Yes, because the lockfile will now specify the engine per dep due to enabling strict engine setting so we get less of those peer: true inconsistencies we got before.

[github-actions]

_{reported by reviewdog 🐶}
[npm-audit] Serialize JavaScript is Vulnerable to RCE via RegExp.flags and Date.prototype.toISOString()

See GHSA-5c6j-r48x-rmvq
Cc @thypon @kdenhartog