Upgrade Node.js version from 20 to 24

[sebdanielsson]

Summary by CodeRabbit

• Chores
  • Updated GitHub Action runtime environment to Node 24, providing access to the latest runtime features and improvements while maintaining full compatibility with existing workflows.

[coderabbitai]

📝 Walkthrough

Walkthrough

The GitHub Action runtime configuration in action.yml was updated from Node.js 20 to Node.js 24. The entrypoint file and all other action metadata remain unchanged.

Changes

Cohort / File(s)	Summary
GitHub Action Configuration action.yml	Updated runs.using from node20 to node24 to leverage the newer Node.js runtime version.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hop, hop, hooray!
From twenty to twenty-four we hop today,
A faster Node beneath the GitHub sky,
The Action hops along, updated and spry! 🚀

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and directly describes the main change: upgrading the Node.js runtime version in action.yml from node20 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

---

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.}

[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 `@action.yml`:
- Line 27: The action's runtime was changed to "using: node24" which introduces
breaking compatibility requirements; update your release notes and changelog to
explicitly state Node 24 compatibility and required infrastructure (self-hosted
runner v2.327.1+ and GHES 3.14+), mention Linux ARM32 auto-fallback to Node 20
and the potential failures on unsupported runners/GHES, and publish the action
under a new major version tag (e.g., v2) to signal the breaking change so
consumers can opt in; locate the "using: node24" entry in action.yml to guide
the documentation and version bump.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cf1835d9-52b2-40c7-9f1c-69e5a24ae1d8

📥 Commits

Reviewing files that changed from the base of the PR and between 6c366f5 and e34d1b1.

📒 Files selected for processing (1)

• action.yml

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

What are the current compatibility requirements for GitHub Actions JavaScript actions using runs.using: node24 (minimum GHES version, minimum self-hosted runner version, and unsupported OS/architectures)?

💡 Result:

Current compatibility requirements for GitHub Actions JavaScript actions using runs.using: node24: - Minimum self-hosted runner version: v2.327.1 (added support via PR #3940) - Minimum GHES version: Not explicitly found; likely GHES 3.14+ based on runner upgrades, but recommend latest GHES for full support. Progressive rollout means check specific instance. - Unsupported OS/architectures: Linux ARM32 (automatic fallback to Node 20 with warning) As of 2026-03-28, Node 24 is the default/enforced for JS actions (phased migration complete per June 2026 timeline), with enforcement in recent runners like v2.333.0.

Citations:

• 1: Node 20 -> Node 24 migration feature flagging, opt-in and opt-out environment variables actions/runner#3948
• 2: https://github.com/actions/setup-node
• 3: https://github.blog/changelog/2026-02-05-github-actions-self-hosted-runner-minimum-version-enforcement-extended/
• 4: https://docs.github.com/en/actions/reference/runners/self-hosted-runners
• 5: https://github.com/actions/runner/releases/tag/v2.327.1
• 6: https://github.com/actions/runner/blob/main/releaseNote.md

---

Document Node 24 compatibility requirements in release notes and use a major version tag.

The node24 runtime requirement affects self-hosted runners and GHES deployments. Requires self-hosted runner v2.327.1+ and GHES 3.14+ (verify with your instance). Linux ARM32 systems will auto-fallback to Node 20, but other users on unsupported runner/GHES versions may experience failures. Add explicit compatibility notes to release documentation and consider shipping as a major version to signal the breaking change to consumers.

🤖 Prompt for AI Agents

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

In `@action.yml` at line 27, The action's runtime was changed to "using: node24"
which introduces breaking compatibility requirements; update your release notes
and changelog to explicitly state Node 24 compatibility and required
infrastructure (self-hosted runner v2.327.1+ and GHES 3.14+), mention Linux
ARM32 auto-fallback to Node 20 and the potential failures on unsupported
runners/GHES, and publish the action under a new major version tag (e.g., v2) to
signal the breaking change so consumers can opt in; locate the "using: node24"
entry in action.yml to guide the documentation and version bump.