Merged
Conversation
github-actions
bot
force-pushed
the
sync-uv-lock
branch
3 times, most recently
from
93147a4 to
057fa3e
Compare
github-actions
bot
force-pushed
the
sync-uv-lock
branch
from
057fa3e to
093d30e
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. Only creates a PR when the lock file contains real dependency changes (timestamp-only noise is detected and skipped). See thesync-uv-lockjob documentation for details.Configuration
Relevant
[tool.repomatic]options:Tip
If you suspect the PR content is outdated, click
Run workflowto refresh it manually before merging.Workflow metadatapushmain0b8739d8sync-uv-lockrenovate.yaml🏭 Generated with repomatic