Skip to content

deps: ruff 0.16.1, ty 0.0.65 - #69

Merged
vvillait88 merged 3 commits into
mainfrom
deps/sweep
Jul 31, 2026
Merged

deps: ruff 0.16.1, ty 0.0.65#69
vvillait88 merged 3 commits into
mainfrom
deps/sweep

Conversation

@vvillait88

Copy link
Copy Markdown
Contributor

Summary

Routine dev-tooling bumps from the workspace-wide maintenance sweep: ruff 0.16.0 to 0.16.1 and ty 0.0.63 to 0.0.65. Lockfile only, no source changes.

Type of change

  • Bug fix (no breaking change)
  • New feature (no breaking change)
  • Breaking change (existing callers must update)
  • Docs, tests, or internal maintenance only

Public API

None. Both are lint/typecheck tooling; no exported type, signature, or wire format changes, so callers have no migration to make.

Test plan

Ran the repo's full Python gate set with exit codes read directly: ruff check clean, ruff format --check clean at 21 files, ty check clean, pytest 183 passed with 8 skipped, and vulture --min-confidence 80 clean over the package. Every sync used --all-extras --all-groups rather than a bare uv sync, which would resolve base deps only and quietly strip the venv's extras and dependency groups.

Checklist

  • Tests cover the new behavior, and the suite passes locally
  • Lint, format, and type checks pass
  • Docs and README examples updated if the public surface changed
  • No secrets, credentials, or personal data in the diff or the tests

vvillait88 and others added 3 commits July 30, 2026 22:25
Dev tooling only, both lockfile-level. Synced with --all-extras
--all-groups throughout, never bare, so the venv keeps its extras and
dependency groups.

Gates: ruff check, ruff format --check, ty check, pytest (183 passed, 8
skipped) and vulture all clean.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Dependency movement only; no public API, signature, or wire format change,
so this is a patch bump. Release notes belong in the GitHub Release body at
tag time.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
uv.lock embeds the project's OWN version, so a pyproject.toml bump leaves the
lock disagreeing with the manifest about what this package is. Nothing errors
and no gate notices, exactly like the bun equivalent where `bun update`
leaves the lock's embedded ranges stale.

Run `uv lock` after any version bump, before committing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@vvillait88
vvillait88 merged commit a067a21 into main Jul 31, 2026
8 checks passed
@vvillait88
vvillait88 deleted the deps/sweep branch July 31, 2026 06:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant