{{ message }}
Repository navigation
Commit e67c011
committed
py(deps[dev]) Require ruff>=0.16.1
why: A bug-fix release: no newly stabilized rules and no change to the
default rule set, so it surfaces no new diagnostics here. Verified by
running ruff against this repo at both versions; the finding set is
identical.
What it does change is three rules that were over-firing. B008 now
treats `range` as immutable, RET504 stops firing when the variable is
read in a `finally` clause, and D214, D405 and D413 skip section
detection inside RST directive bodies.
The floor earns its keep on fix safety rather than findings: 0.16.1
reclassifies PT022 and FURB105 fixes as unsafe, so a contributor still
resolving 0.16.0 would have `ruff check --fix` apply edits this
version now declines to make.
0.16.2 exists but is younger than the 3-day supply-chain cooldown and
is deliberately not taken.
what:
- ruff>=0.16.0 -> ruff>=0.16.1 in both pin sites (dev and lint groups)
- uv.lock: ruff 0.16.0 -> 0.16.1
See also: https://github.com/astral-sh/ruff/releases/tag/0.16.11 parent c6d6d2e commit e67c011
2 files changed
Lines changed: 25 additions & 25 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments