Repository navigation
ruff-pre-commit is pinned to v0.17.0, the newest tag - #342
Conversation
The prek-pins-current hook refuses a pre-commit pin that is not the newest tag, and ruff-pre-commit published v0.17.0 on 2026-10-09. From then on the hook failed on main and on every branch cut from it, a failure that had nothing to do with the change under test. Only .pre-commit-config.yaml changes. Nothing else in the repository declares ruff's version: toolchain.toml names the tool without a version, the lefthook entries and the CI pipx install run whatever ruff is on PATH, and ruff.toml has no required-version. Ruff 0.17.0 reports no findings and reformats no file here. Its breaking changes move the default target version and the default rule set, and ruff.toml sets both explicitly (py311 and its own select list), so neither reaches this repository. Claude-Session: https://claude.ai/code/session_01TG5hbR4Re6gcEZTpBCBymc
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe Ruff pre-commit repository revision changes from ChangesRuff pre-commit hook
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to This updates the Ruff version used by the pre-commit hooks; the referenced revision provides the configured hooks and the repository’s Ruff settings remain explicit. No specific workflow regression is established, so the update is mergeable subject to normal checks. Pre-merge checks |
 |
| Check name | Status | Explanation |
|---|---|---|
| Description Check |  |
Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check | |
The title clearly and concisely states the main change: updating the ruff-pre-commit pin to v0.17.0. It matches the pull request changes and objective. |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
✨ Finishing Touches
🧪 Generate unit tests (beta)
- Commit to this branch
- Create a new PR
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
Comment @coderabbitai help to get the list of available commands.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #342 +/- ##
=======================================
Coverage 94.37% 94.37%
=======================================
Files 46 46
Lines 23091 23091
=======================================
Hits 21792 21792
Misses 1299 1299 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
2 participants
The prek-pins-current hook refuses a hook
rev:that is not the newest tag of its repository. ruff-pre-commit published v0.17.0, so every branch's prek leg, local and in CI, was failing on a line nobody had changed. This bumps that one pin from v0.16.10 to v0.17.0.No other file declares ruff's version: toolchain.toml lists ruff unversioned, lefthook and CI run the ruff on PATH, and ruff.toml has no
required-version.ruff 0.17.0 reports no findings and reformats nothing here. Its breaking changes (the default target moving to Python 3.11 and the new default rule set) do not apply, because ruff.toml sets
target-versionandselectexplicitly.https://claude.ai/code/session_01TG5hbR4Re6gcEZTpBCBymc
Summary by CodeRabbit