Upgrade ruff to 0.16.6 and ty to 0.0.78 - #124
Merged
Merged
Conversation
Both stayed within their existing pyproject constraints (ruff's <0.17 cap, ty's unpinned upper bound), so this is a lockfile refresh plus the ty lower-bound bump. ruff check/format and ty check both pass clean against the new versions with no new findings, so there's nothing to fix up as part of the upgrade. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01R5KU4wBRARfY8VKiAMj1Gj
davegaeddert
marked this pull request as ready for review
September 8, 2026 19:53
davegaeddert
enabled auto-merge (squash)
September 8, 2026 19:53
PASS: 1 review scope passed, 1 agent approved
✅ codex approved Next steps:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ruff0.16.4 → 0.16.6 andty0.0.74 → 0.0.78, refreshinguv.locktylower bound inpyproject.tomlto>=0.0.78(ruff stayed within its existing>=0.16.2,<0.17constraint, so no pyproject change was needed there)Checked both changelogs for anything actionable:
PT020autofix,TID254/TID255fix-loop fix), bug fixes (B031panic,RUF102, duplicatePT017diagnostics), no new stable-default rules that fired against this codebasedisjoint-castdiagnostic, deprecation reporting for intersection property accessors/implicit constructor calls/overloads, plus a batch of narrowing/inference/protocol correctness fixesVerification
ruff check,ruff format --check, andty checkall pass clean against the whole workspace with the new versions — no new findings, so there was nothing to fix up (and nothing to remove) as part of this bump.Note: this sandbox has no Docker/Postgres available, so
./scripts/testcouldn't be run here. The change itself is scoped to the lockfile and one version constraint, verified via ruff/ty directly.Test plan
uv run ruff check .(plain's bundled config) — all checks passeduv run ruff format --check .(plain's bundled config) — all files already formatteduv run ty check .— all checks passeduv run plain-code check . --skip-oxc— ruff, ty, and annotation checks all pass./scripts/test— not run; no Docker/Postgres in this environment🤖 Generated with Claude Code
https://claude.ai/code/session_01R5KU4wBRARfY8VKiAMj1Gj
Generated by Claude Code