fix(ci): pin the ruff download checksum in CI

[wizzomafizzo]

Applies the same fix as #9 to ci.yml, which was left with the identical gap.

astral-sh/ruff-action v4.1.0 ships KNOWN_CHECKSUMS only up to ruff 0.15.20, and skips manifest checksums entirely unless manifest-file is set:

// For the default astral-sh/versions source, checksum validation relies on
// user input or the built-in KNOWN_CHECKSUMS table, not manifest sha256 values.

With version: "0.16.0" and no checksum input, validateChecksum finds no known checksum, leaves isValid as undefined, and verifies nothing — while downloading from the Astral CDN mirror the action prefers by default.

Fix

Pass the SHA-256 of ruff-x86_64-unknown-linux-gnu.tar.gz, the artifact selected for ubuntu-latest (x86_64 + unknown-linux-gnu). Same runner, action pin, and ruff version as the release workflow, so the value matches the one already in release.yml.

Provenance

The checksum comes from the published ruff-x86_64-unknown-linux-gnu.tar.gz.sha256 asset on the ruff 0.16.0 release, independently confirmed by downloading the tarball, hashing it, and running the extracted binary to check it reports ruff 0.16.0. It is already proven in CI: the v1.0.0 release run passed with this exact value.

Note

An explicit checksum is single-platform. If runs-on ever moves off x86_64 linux this fails loudly with a mismatch rather than silently installing something else, but it is a maintenance point when bumping the ruff version — both workflows now need updating together.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 22 minutes

Limit details: You’ve used the included review currently available. Your 91 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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 within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 05b01561-b9e1-4b4b-b4e3-7d77e42fc36e

📥 Commits

Reviewing files that changed from the base of the PR and between 19bd9b9 and 5352551.

📒 Files selected for processing (1)

• .github/workflows/ci.yml

---

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