fix(ci): use Node 24-native reviewer actions on latest main

[seonghobae]

Purpose

Remove the live reviewer-ci Node.js 20 action-runtime deprecation warning by replacing checkout and Python setup with immutable official Node 24-native action commits. This is a clean protected-main successor to frozen RED Draft #245 after scheduler PR #244 advanced main; neither predecessor branch nor history is rebased or force-pushed.

Exact identity and scope

• live protected base at construction and PR creation: 84a1b4cc0f781fc35fae66a47ada0b099aa2555d;
• exact successor head: ebf92938b536f786c8587c949a2f5a2036a984b7;
• exact successor tree: baab67674877a156c516236fafd880b2ed225be2;
• comparison: one commit ahead, zero behind;
• exact changed paths:
  • .github/workflows/reviewer-ci.yml — blob d3f37e7ed4c0d05d7c2cf45be13d2f340fff6eb4;
  • test/reviewer-ci-action-runtime-integrity.test.ts — blob 740cadf5069bfd726cf804dd2bb40551fda10985.

The workflow diff changes only:

• actions/checkout from exact old Node 20 commit to 3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1;
• actions/setup-python from exact old Node 20 commit to 5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0.

Official action metadata at both proposed exact commits declares runs.using: node24. Every scheduler, release, package, security, and documentation byte from current protected main, including #244, is inherited unchanged.

Test-first evidence

Frozen predecessor Draft #245 supplied the deliberate RED against the same protected workflow blob:

• RED exact head 9e1f8e5fc377d795fe3660a10e5b962f0c2cc6c3;
• exact test blob 740cadf5069bfd726cf804dd2bb40551fda10985;
• application CI run 31653408209, job/check 94302426161, terminal failure exactly at reviewer CI action runtime integrity > uses immutable Node 24-native GitHub actions;
• a deterministic exact-blob harness separately reproduced the missing new-pin assertion.

The narrow GREEN changes only the two immutable action pins. The identical four focused assertions pass against the exact GREEN workflow blob. No predecessor CI, scanner, review, model, release, deployment, or production evidence transfers to this successor.

Evidence boundary

This exact successor head must obtain fresh terminal-success application ci, reviewer-ci, protected-base-eligible central Security Scan, CodeQL, and every other applicable check against an unchanged live base. The final reviewer job annotations must also prove the Node 20 warning is absent. Pending, queued, skipped, absent, neutral, failed, cancelled, stale, predecessor, status-only, model-only, or rate-limited evidence is non-passing.

Immediately before merge, independently re-resolve live base/head, verify one-ahead/zero-behind ancestry and exact check checkout SHA, re-read live rulesets and central .github Security Scan authority, and require zero valid unresolved findings. Independent non-author approval is required only if live policy actually requires it.

This change does not publish a release, prove deployment or production operation, select an outbound license, or establish commercial/acquisition readiness. #245 is superseded only after this exact successor is protected and independently reverified.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 108 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5b86a386-3292-4b6e-8228-32e2572b87ab

📥 Commits

Reviewing files that changed from the base of the PR and between 84a1b4c and ebf9293.

📒 Files selected for processing (2)

• .github/workflows/reviewer-ci.yml
• test/reviewer-ci-action-runtime-integrity.test.ts

---

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