ci: update CLI release test matrix to Node 24+

[paulbalaji]

Summary

• Removed Node 20-23 from CLI cross-platform release test matrix
• Prisma 7 requires Node 24 minimum

Test plan

• CI passes on Node 24 and 25 across all platforms

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • CI now runs cross-platform release tests on a narrower set of Node.js versions, reducing tested environments.
  • CI caches Foundry binaries to reduce installation time and lower CI runtime for workflows.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Two CI edits: the release workflow narrows the Node.js matrix for the cross-platform release test to Node 24 and 25; the custom setup-foundry composite action adds a caching step for Foundry under ~/.foundry keyed by OS and foundry version.

Changes

Cohort / File(s)	Summary
Workflow Configuration .github/workflows/release.yml	Reduced node-version matrix for cli-install-cross-platform-release-test job from [20, 21, 22, 23, 24, 25] to [24, 25].
Foundry setup action .github/actions/setup-foundry/action.yml	Added a "Cache Foundry" step using actions/cache@v5 to restore/save ~/.foundry with a key composed of runner OS and the emitted foundry version; placed before installation.

Sequence Diagram(s)

mermaid
sequenceDiagram
participant Workflow as CI Workflow
participant Runner as Runner (ubuntu/...)
participant Cache as actions/cache@v5
participant Installer as Install Foundry step
Workflow->>Runner: start job
Runner->>Cache: restore cache (~/.foundry) with key: OS + FOUNDRY_VERSION
alt cache hit
Cache-->>Runner: cached Foundry provided
else cache miss
Cache-->>Runner: no cache
end
Runner->>Installer: run Install Foundry (may use cached files)
Installer-->>Runner: install binaries / emit FOUNDRY_VERSION
Runner->>Cache: save cache with key: OS + FOUNDRY_VERSION

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• fix(ci): mitigate flaky Hardhat compiler download #7864: Adds a caching step to .github/actions/setup-foundry/action.yml, touching the same composite action.
• fix(ci): skip bytecode check on release PRs and add foundry to CLI install #7588: Integrates or modifies Foundry setup in CI workflows; related to installation/cache steps.
• fix(docker): switch back to Alpine base image #7564: Adjusts Foundry installation/version propagation in CI; overlaps with installer/version handling.

Suggested reviewers

• xeno097
• yorhodes
• larryob

Poem

In the bog of CI I take a stroll,
Trimming Node rows to a smaller shoal.
Foundry tucked in a cozy cache bed,
Builds wake up faster, no more dread. 🧅✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description covers key sections (summary of changes and rationale), but omits several template sections like drive-by changes, related issues, backward compatibility, and testing details.	Complete the missing template sections: specify any drive-by changes (like the Foundry caching addition), link related issues, clarify backward compatibility implications, and provide testing details beyond the checkbox.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: updating the CLI release test matrix to Node 24+, which directly corresponds to the primary modification in the changeset.
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 pb/cifix

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.02%. Comparing base (c89997d) to head (43995e7).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7944   +/-   ##
=======================================
  Coverage   77.02%   77.02%           
=======================================
  Files         117      117           
  Lines        2651     2651           
  Branches      244      244           
=======================================
  Hits         2042     2042           
  Misses        593      593           
  Partials       16       16           

Components	Coverage Δ
core	87.80% <ø> (ø)
hooks	71.86% <ø> (ø)
isms	81.10% <ø> (ø)
token	86.67% <ø> (ø)
middlewares	84.98% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.