feat!: use node version 24

[CodeReaper]

Resolves #719.

Summary by CodeRabbit

• Chores
  • Raised the minimum Node.js requirement to version 24.
  • Updated TypeScript/Node type definitions to match the newer Node version.
  • Switched the action/runtime environment to use Node.js 24 for CI/runtime consistency.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 60363edd-037b-4e13-b0d0-c076f7a83d55

📥 Commits

Reviewing files that changed from the base of the PR and between 89a0eb7 and e555937.

📒 Files selected for processing (1)

• action.yml

✅ Files skipped from review due to trivial changes (1)

• action.yml

---

📝 Walkthrough

Walkthrough

Updates Node.js target from 20 to 24: package.json bumps engines.node and @types/node; action.yml changes the GitHub Action runtime to Node.js 24. No changes to exported or public API declarations.

Changes

Cohort / File(s)	Summary
Package manifest package.json	Bumped engines.node from >=20 to >=24; updated devDependency @types/node from 20.8.2 to 24.12.0.
Action runtime action.yml	Changed action runtime from Node.js 20 to Node.js 24 (runs.using image/runtime update).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐇 I hopped from v20 to v24,
Fresh types and runner at the door.
No more warnings, code sings anew,
A carrot-flavored build—yay, woohoo! 🥕

🚥 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 'feat!: use node version 24' directly and clearly describes the main change—upgrading to Node.js 24 across the codebase.
Linked Issues check	✅ Passed	The PR successfully addresses issue #719 by updating to Node.js 24 in package.json (engines.node >=24) and action.yml runtime, eliminating Node.js 20 deprecation warnings.
Out of Scope Changes check	✅ Passed	All changes are scoped to resolving Node.js 20 deprecation: package.json @types/node version and engines.node updated, action.yml runtime upgraded to node24.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

📝 Coding Plan

• Generate coding plan for human review comments

---

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 and usage tips.}

Tip

You can disable sequence diagrams in the walkthrough.

Disable the reviews.sequence_diagrams setting to disable sequence diagrams in the walkthrough.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@package.json`:
- Line 39: The project updated package.json engines to "node": ">=24" but
action.yml still declares the GitHub Actions runtime as node20; open action.yml
and change the runs.using value from "node20" to "node24" (and ensure any
related mentions of Node 20 in that file are updated consistently), keeping the
action.yml metadata aligned with package.json to eliminate the Node 20
deprecation warning.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5649a0e9-84de-4416-8908-babd95f29629

📥 Commits

Reviewing files that changed from the base of the PR and between 1539a6a and 89a0eb7.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json