chore: weekly uv lockfile upgrade - #51
Merged
Merged
Conversation
DKZed
force-pushed
the
chore/uv-lock-upgrade
branch
from
May 31, 2026 07:13
4ee0499 to
c423530
Compare
DKZed
force-pushed
the
chore/uv-lock-upgrade
branch
from
June 7, 2026 07:18
c423530 to
757e87f
Compare
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.
Automated weekly run of
uv lock --upgrade.This refreshes
uv.lockto the latest versions of alltransitive dependencies allowed by each package's
pyproject.tomlconstraints, picking up any upstreamsecurity patches.
CI on this PR will verify the upgraded dependencies still
pass lint, type-check, and the Aerospike-backed test
matrix (Python 3.10 and 3.13). Merge if green; otherwise
investigate the failing dependency before merging.