Bump ruff from 0.15.18 to 0.16.1 - #233
Conversation
🔵 Review postedLast updated: 2026-08-01 01:01 UTC |
rtibblesbot
left a comment
There was a problem hiding this comment.
PR #233 — dependency review: ruff 0.15.18 → 0.16.0, dev-only ([dependency-groups].dev), lockfile-only diff (21/21 lines in the ruff block, no new transitive deps).
Semver risk: 0.x minor — breaking under ruff's own versioning.
Breaking changes: the headline one is the default rule set expanding 59 → 413 rules. It does not apply here: pyproject.toml sets select = ["E", "F", "W", "C90", "I"], so defaults are never consulted, and the 18 rules dropped from defaults (E401, E402, E711, E712, E741, F403, F405, …) are still covered by the explicit E/F selectors. Also new: ruff format now formats Python code blocks in Markdown by default (0.16.0 walks 45 files vs 0.15.18's 42 — CHANGELOG.md, README.md, docs/README.md; all already conformant), and ruff: ignore comments (additive, unused here). No removed config options, no target-version impact.
Security fixes: none. Peer/transitive changes: none — ruff ships dependency-free wheels.
Compatibility: verified locally against this branch — ruff@0.16.0 check → all checks passed; ruff@0.16.0 format --check → 45 files already formatted. No code changes required.
CI: failing, but not from this bump. The Linting workflow fails on the rebuild-from-specs hook regenerating js/package.json 0.2.18 → 0.2.19 (setuptools-scm resolves a post-tag dev version on PR branches). All ruff-driven hooks passed in the same run. The identical failure reproduces on PR #230, which touches no Python tooling at all, and on #231/#232; main was last green at 3dc6503. Needs a separate fix (tag the release, or make version regeneration tolerate dev versions), not one inside this dependabot PR. Python tests was still queued at review time — worth a glance before merge.
Follow-up (out of scope): .pre-commit-config.yaml pins astral-sh/ruff-pre-commit at v0.15.7 and dependabot.yml registers no pre-commit ecosystem, so this bump only reaches make build — the hooks that actually gate CI stay on 0.15.7. Pre-existing skew, worth its own issue.
COMMENT rather than APPROVE solely because CI is red.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Ran a dependency-update review pipeline over the version bump:
- Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
- Extracted the changelog and release notes across the version range
- Assessed compatibility with this project's usage and whether any code changes are required
- Treated CI as the primary safety net
- Scaled the review depth to the update's risk
- Chose the verdict from semver risk, changelog findings, and CI status
|
@dependabot rebase |
Bumps [ruff](https://github.com/astral-sh/ruff) from 0.15.18 to 0.16.1. - [Release notes](https://github.com/astral-sh/ruff/releases) - [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md) - [Commits](astral-sh/ruff@0.15.18...0.16.1) --- updated-dependencies: - dependency-name: ruff dependency-version: 0.16.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
db0b400 to
a194c04
Compare
Bumps ruff from 0.15.18 to 0.16.1.
Release notes
Sourced from ruff's releases.
... (truncated)
Changelog
Sourced from ruff's changelog.
... (truncated)
Commits
80790b3Bump 0.16.1 (#27330)63830f3[ty] Borrow from constraint set storage less often (#27328)f40dca9[ty] Preserve forwarded expanded-variadic diagnostic sources (#27266)0d80497Lint TOML files in the LSP (#26862)d91586bUpdate prek dependencies (#27293)7da4b8b[ty] Respect bounds and constraints in generic materializations (#27228)b20daf7[ty] refactor: add helper function to send partial results (#27249)4d4c8fa[ty] Emit diagnostic when specializing a non-generic class (#26883)7c3e2db[ty] Fix enum class container assignability (#27318)d5ef97f[flake8-return] Fix false positive when variable is read infinallyclaus...