Sync uv.lock#1800
Merged
Merged
Conversation
kdeldycke
force-pushed
the
sync-uv-lock
branch
4 times, most recently
from
June 29, 2026 08:01
cd2dbd8 to
8a15dec
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-06-23.7.14.1→7.14.32.0→2.1.010.21.3→11.0🔜 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.2.63.08.4.18.4.22026.5.12026.6.33.11.03.12.010.110.20.8.10.8.2Release notes
coverage7.14.2Version 7.14.2 — 2026-06-20
coverage json -o -useless for capturing JSON output. Now messages are written to stderr, fixing issue 2197.CoverageDatakept one SQLite connection per thread that recorded coverage, but never closed them when those threads terminated. On long runs with many short-lived threads this leaked one file descriptor per dead thread, eventually failing withOSError: [Errno 24] Too many open files. Connections belonging to terminated threads are now closed and dropped. Fixes issue 2192. Thanks, Matthew Lloyd.COVERAGE_IDtool id. But other tools might also assume they could use that id. Pre-allocated ids don’t really make sense, so now we search for a usable one instead. Fixes issue 2187.➡️ PyPI page: coverage 7.14.2.
➡️ To install:
python3 -m pip install coverage==7.14.27.14.3Version 7.14.3 — 2026-06-22
...exclusion rule now also matches function bodies whose closing return-type bracket is on its own line (for example, after a long-> dict[ ... ]annotation that a formatter has split over multiple lines). Closes issue 2185, thanks Mengjia Shang.Couldn't import C tracererrors. We can’t import the C tracer because in 7.14.2 we stopped shipping compiled wheels for 3.13t. Thanks, Hugo van Kemenade.➡️ PyPI page: coverage 7.14.3.
➡️ To install:
python3 -m pip install coverage==7.14.3deepmergev2.1.0What's Changed
New Contributors
Full Changelog: https://redirect.github.com/toumorokoshi/deepmerge/compare/v2.0...v2.0.1
pymdown-extensions11.011.0
base_pathby default. Can be disabled by setting newrestrict_pathoption to
False. The newroot_pathcan be specified if paths are desired to be restricted to a differentlocation separate
base_pathwhich is also used as a relative base for image paths.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 metadatapushmain93669270sync-uv-lockautofix.yaml🏭 Generated with repomatic
6.31.0