[vvillait88]

Summary

Maintenance sweep, lock refresh only: pytest-asyncio 1.4.0 to 1.4.1 and ty 0.0.91 to 0.0.92, both dev tools. The pyproject floors already admit both, so no manifest change. No release: the wheel does not change.

Checked and found current: every runtime dependency, the GitHub Actions pins, the uv version pinned in the workflows (0.13.5), the osv-scanner release (2.7.0), and the lock (no prerelease versions).

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

Test plan

Ran the CI gate set on Python 3.15 with the new lock: uv sync --frozen --all-extras --all-groups, ruff check, ruff format --check, ty check, vulture and pytest (172 passed, 2 skipped). Every gate exited 0.

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 public change)
• No secrets, credentials, or personal data in the diff or the tests

[vvillait88]

Review: approve.

• Diff is uv.lock only (+22/-22, two hunks). The only name/version lines that move are pytest-asyncio 1.4.0 to 1.4.1 and ty 0.0.91 to 0.0.92; no other package entry changes.
• PyPI latest re-read: pytest-asyncio 1.4.1, ty 0.0.92. Both are dev tools, so no release is owed.
• CI: 13 of 13 rows pass (test 3.11 to 3.15, ci, Dependency Scan, Python Audit, CodeQL).
• Body carries every template heading with the boxes ticked. Minor: it has no "worked with" line (the repo template has no slot for it, so non-blocking).