Sync uv.lock#1829
Merged
Merged
Conversation
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-07-13.7.15.0→7.15.10.22.3.20260518→0.22.3.2026071210.2.1→11.0Release notes
coverage7.15.1Version 7.15.1 — 2026-07-12
show_contextsenabled, a context label containing</script>(for example a parametrized pytest node id) could close the inline<script>element in a file page early, injecting markup. Context labels are now fully escaped. Thanks, Rajath Mohare.➡️ PyPI page: coverage 7.15.1.
➡️ To install:
python3 -m pip install coverage==7.15.1types-docutilsChangelog
wcmatch11.011.0
EXTGLOB/EXTMATCHregular expression patterns when possible to reduce deeplynested patterns.
<0-9>) via newNUMRANGEflag.EXTGLOB/EXTMATCHwas enabled. Due to the new feature added that reduces extended glob group nesting, groups nolonger appear exactly as specified. Moving forward, capturing groups are not included by default. If you need the
old behavior, it can be enabled in a
translate()call via theCAPTUREflag. This flag will cause extended globreduction to be turned off and for capturing groups to be enabled.
EXTGLOB/EXTMATCHparsing once an unclosed extended glob pattern is encountered.SPLITnot accounting for POSIX character class.🔜 Held back by cooldown
Newer releases already published but withheld because they are still inside the
exclude-newercooldown window. Each becomes lockable on its eligible date.26.0.026.1.07.15.17.15.213.1.013.3.14.10.04.10.12.8.42.92.0.32.1.00.15.00.15.1Configuration
Relevant
[tool.repomatic]options:uv-lock.syncImportant
If you suspect the PR content is outdated, click
Run workflowto refresh it manually before merging.Workflow metadataschedulemain208ee51fsync-depsautofix.yaml🏭 Generated with repomatic
7.1.0