ci: bump actions to Node 24 runtimes

[igun997]

Why

The first Build & Release run on master succeeded but every job emitted:

Node.js 20 is deprecated. The following actions target Node.js 20 but are being
forced to run on Node.js 24: actions/checkout@v4, actions/setup-go@v5, ...

Changes

Action	Was	Now
actions/checkout	v4	v7
actions/setup-go	v5	v7
actions/upload-artifact	v4	v7
actions/download-artifact	v4	v8
actions/attest-build-provenance	v2	v4
docker/setup-qemu-action	v3	v4
docker/setup-buildx-action	v3	v4
docker/login-action	v3	v4
docker/metadata-action	v5	v6
docker/build-push-action	v6	v7
softprops/action-gh-release	v2	v3

Checked each major's release notes: they are Node 24 runtime / ESM migrations. No input API changes affect the inputs used here. Two worth noting, neither of which applies:

• download-artifact@v8 skips auto-unzip for direct (unarchived) uploads. Our artifacts are zipped by upload-artifact defaults, so extraction still happens; pattern + merge-multiple are unchanged.
• checkout@v7 blocks fork PR checkout for pull_request_target / workflow_run. Neither trigger is used.

Verified locally: both workflow files still parse as valid YAML. This PR run exercises ci.yml with the new versions; release.yml is exercised on merge.

[coderabbitai]

Warning

Review limit reached

@igun997, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: cf7677df-262b-4685-93c1-c2dcad0457b8

📥 Commits

Reviewing files that changed from the base of the PR and between 11f010e and b588e38.

📒 Files selected for processing (2)

• .github/workflows/ci.yml
• .github/workflows/release.yml

---

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