Skip to content

deps: lockfile refresh (fastapi 0.141.1 and transitives) - #102

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

deps: lockfile refresh (fastapi 0.141.1 and transitives)#102
vvillait88 merged 5 commits into
mainfrom
deps/sweep

Conversation

@vvillait88

Copy link
Copy Markdown
Contributor

Summary

Lockfile refresh from the workspace-wide maintenance sweep. Ten packages moved, all transitive or dev tooling, the most notable being fastapi 0.140.0 to 0.141.1. No source changes and no direct-dependency range edits.

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. fastapi is a peer the middleware integrates against rather than something re-exported, and its declared range is unchanged, so an installing consumer resolves exactly as before. No exported type, signature, or wire format changes.

Test plan

Ran the repo's full Python gate set with exit codes read directly: ruff check clean, ruff format --check clean at 215 files, ty check clean, pytest 1841 passed with 4 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, breaking test collection.

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 5 commits July 30, 2026 22:26
…ers)

Transitive and dev-tooling movement from uv lock --upgrade. 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 (1841 passed, 4
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>
Picks up the SDK released from this same sweep. The declared constraint is
>=2.6.0, which 2.6.1 already satisfied, so the lock had to be moved
explicitly with --upgrade-package; a resolution that still satisfies its
constraint never re-resolves on its own.

Constraint left at >=2.6.0 deliberately: nothing here requires the newer
patch, and raising a published library's floor forces work on every consumer
for no gain.

Gates: ruff check, ruff format --check, ty check, pytest (1841 passed, 4
skipped) and vulture all clean. Synced with --all-extras --all-groups.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Stated rather than incidental: the constraint now names the version the lock
resolves, so a fresh install cannot quietly land on an older SDK.

Gates: ruff check, ruff format --check, ty check and pytest (1841 passed, 4
skipped) all clean.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@vvillait88
vvillait88 merged commit 1a359e0 into main Jul 31, 2026
8 checks passed
@vvillait88
vvillait88 deleted the deps/sweep branch July 31, 2026 06:26
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