Repository navigation
chore(deps): commit uv.lock and upgrade all dependencies - #53
Merged
Merged
Conversation
Every CI job resolved dependencies on its own, so one run could mix versions. The Dockerfile now installs from the lock too.
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
1 participant
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.
uv.lockwas gitignored, so every CI job resolved its dependencies from scratch. Two jobs in the same run could end up on different versions. The main run at 3e27d65 passed only becausepytest (app)got db-retry 0.7.0 while other jobs had already installed 0.7.1. On 0.7.1 the then-strict xfail intest_connection_loss.pywould have XPASSed and failed the run.This PR commits the lockfile, with every dependency upgraded (
uv lock --upgrade, 56 packages). CI'suv syncuses it as is. The Dockerfile now copiesuv.locknext topyproject.tomlbeforeuv sync, sojust testalso runs against the locked versions.just installstill runsuv lock --upgrade, which is now how the lock gets bumped.Notable upgrades: ruff 0.16.4 to 0.17.1, ty 0.0.73 to 0.0.89, lite-bootstrap 1.4.0 to 1.13.0, multidict 6.7.1 to 7.1.0, asyncpg 0.31.0 to 0.32.0, alembic 1.19.1 to 1.20.0, pytest-alembic 0.12.1 to 0.13.1, opentelemetry 1.44 to 1.45 (instrumentation 0.65b0 to 0.66b1), and pydantic 2.13.4 to 2.14.1.
Verified locally against the new lock:
ruff format --check,ruff checkandty checkpass with no code changes.just test: 129 passed, 100% coverage. The container reported db-retry 0.7.1 and ruff 0.17.1.just test-migrations: 4 passed.