Sync uv.lock#1727
Merged
Merged
Conversation
kdeldycke
force-pushed
the
sync-uv-lock
branch
4 times, most recently
from
May 29, 2026 05:43
7880f23 to
7c4a80f
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.
Description
Runs
uv lock --upgradeto update transitive dependencies to their latest allowed versions. See thesync-uv-lockjob documentation for details.Updated packages
Resolved with
exclude-newercutoff:2026-05-22.2026.4.22→2026.5.203.15→3.16Release notes
idnaChangelog
Configuration
Relevant
[tool.repomatic]options:uv-lock.syncImportant
If you suspect the PR content is outdated, click
Run workflowto refresh it manually before merging.Workflow metadatapushmainb33d5468sync-uv-lockautofix.yaml🏭 Generated with repomatic
6.22.0