fix(ci): run on Node 22 and pin pnpm 11.1.2

[AhmedFr]

What & why

Fixes the CI workflow added in #3, which failed on its first run.

pnpm/action-setup's floating version: 11 resolved to pnpm 11.7.0, which
requires Node ≥ 22.13. The workflow pinned Node 20, so setup-node's pnpm
cache step loaded the Node 22 builtin node:sqlite and crashed with
ERR_UNKNOWN_BUILTIN_MODULE, failing every run in ~15s.

• Move CI to Node 22 (current LTS; the runner is already deprecating Node 20).
• Pin pnpm to the exact local 11.1.2 for reproducible installs.

How it was tested

• pnpm test — 71 passed (local)
• pnpm typecheck
• pnpm lint
• pnpm build
• CI green on this PR — verifying on the PR run before merge

Checklist

• Follows the single-responsibility / per-component folder structure
• No secrets, API keys, or .env values committed
• README / docs updated if behavior or configuration changed — n/a (CI-only change)
• Screenshots included for UI changes — n/a (no UI change)

Screenshots / notes

Root cause traced from the failed run log on #3's merge commit.

[coderabbitai]

Warning

Review limit reached

@AhmedFr, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 57 minutes and 49 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate limits work?

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

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 690d28d8-2e51-4942-99af-7315d767a1c0

📥 Commits

Reviewing files that changed from the base of the PR and between b45d71c and 1eef5da.

📒 Files selected for processing (1)

• .github/workflows/ci.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/ci-node-pnpm-versions

---

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