Update node version to 24.x in CI

[arr00]

Summary by CodeRabbit

• Chores
  • Updated Node.js version from 20.x to 24.x in the build environment.

[netlify]

✅ Deploy Preview for confidential-tokens ready!

Name	Link
🔨 Latest commit	e6c79b5
🔍 Latest deploy log	https://app.netlify.com/projects/confidential-tokens/deploys/69b8496cf293860008d8ddb1
😎 Deploy Preview	https://deploy-preview-328--confidential-tokens.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Walkthrough

The Node.js version in the GitHub Actions setup action was updated from 20.x to 24.x, affecting the build environment configuration used across CI/CD workflows.

Changes

Cohort / File(s)	Summary
GitHub Actions Configuration .github/actions/setup/action.yml	Updated Node.js version from 20.x to 24.x in the setup-node step.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• james-toussaint

Poem

🐰 A hop and a skip through versions new,
From twenty to twenty-four, a Node.js breakthrough!
The rabbits rejoice, their tools now so bright,
With faster updates and newer delights! ✨

🚥 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 clearly and accurately summarizes the main change: updating the Node.js version from 20.x to 24.x in the CI configuration.
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
• Commit unit tests in branch chore/update-npm-version-ci

📝 Coding Plan

• Generate coding plan for human review comments

---

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

Tip

You can disable poems in the walkthrough.

Disable the reviews.poem setting to disable the poems in the walkthrough.

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/actions/setup/action.yml (1)

9-14: ⚠️ Potential issue | 🟠 Major

Include Node major version in cache key to prevent cross-runtime node_modules reuse.

Upgrading to node-version: 24.x while keeping the cache key unchanged creates a risk of restoring node_modules built under a different Node major version. Native modules have version-specific ABIs that break across Node majors, causing flaky CI failures on subsequent runs that restore stale cache entries.

Proposed fix

-        key: npm-v3-${{ hashFiles('**/package-lock.json') }}
+        key: npm-v3-node24-${{ runner.os }}-${{ hashFiles('**/package-lock.json') }}

🤖 Prompt for AI Agents

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

In @.github/actions/setup/action.yml around lines 9 - 14, The cache key for the
actions/cache step ('uses: actions/cache@v4') currently only hashes
package-lock.json and must include the Node major version to avoid restoring
node_modules built for a different runtime; update the cache 'key' expression
(the key field on the cache step) to incorporate the Node major (e.g., include
the node-version or its major) so the cache is namespaced per Node runtime
alongside the existing hash, ensuring separate caches for different Node majors.

🤖 Prompt for all review comments with AI agents

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

Outside diff comments:
In @.github/actions/setup/action.yml:
- Around line 9-14: The cache key for the actions/cache step ('uses:
actions/cache@v4') currently only hashes package-lock.json and must include the
Node major version to avoid restoring node_modules built for a different
runtime; update the cache 'key' expression (the key field on the cache step) to
incorporate the Node major (e.g., include the node-version or its major) so the
cache is namespaced per Node runtime alongside the existing hash, ensuring
separate caches for different Node majors.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5a63f5cd-6406-477c-9ab2-fcebbf26649a

📥 Commits

Reviewing files that changed from the base of the PR and between 5abcb1c and e6c79b5.

📒 Files selected for processing (1)

• .github/actions/setup/action.yml