ci: pin ruff to the version in pyproject dev extra

[FBumann]

Problem

The lint job runs uvx ruff unpinned, so it silently tracks whatever ruff released most recently — while the repo pins ruff==0.15.21 in [dev] (which is what pre-commit and local runs use).

Ruff 0.16.0 shipped recently and began formatting Python code blocks inside Markdown. That flags 26 docs files and fails lint on every open PR regardless of its contents — #755, #754 and #753 are all red on this, and since lint gates test, everything downstream is skipping.

Verified on a clean checkout, same tree, two ruff versions:

ruff	check	format --check
0.15.21 (repo pin)	passed	clean
0.16.0 (what CI used)	passed	26 markdown files flagged

Zero Python files are flagged either way — this is entirely the new Markdown behaviour.

Change

Pin the lint job to the same ruff the dev extra specifies, via a RUFF_VERSION env var alongside the existing PYTHON_VERSION. setup-uv is already pinned to 0.10.9 in this workflow, so this matches the surrounding convention.

Follow-up

This deliberately does not reformat the docs. Adopting 0.16.0 should happen through dependabot #752 (ruff 0.15.21 → 0.16.0), where the 26-file docs reformat can land as a reviewed change together with the bump, and RUFF_VERSION updated in the same PR.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 58 minutes

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 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: 2b3a2310-0572-447b-be24-df56c1078d64

📥 Commits

Reviewing files that changed from the base of the PR and between bc18a54 and 80eba3f.

📒 Files selected for processing (1)

• .github/workflows/tests.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/pin-ruff-version

---

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