chore(deps): update dependency astral-sh/uv to v0.12.0

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Type	Update	Change
astral-sh/uv	uses-with	minor	0.6.3 → 0.12.0

---

Release Notes

astral-sh/uv (astral-sh/uv)

v0.12.0

Compare Source

Released on 2026-07-28.

Since we released uv 0.11.0 in March, we've accumulated changes that improve correctness, safety, and compatibility with specifications, but could break some workflows. This release contains those changes; many have been marked as breaking out of an abundance of caution.

We expect most users to be able to upgrade without making changes.

There are no breaking changes to the configuration of the uv build backend. If your [build-system] table includes an upper bound on uv_build, update it to allow uv_build 0.12, e.g., uv_build>=0.11.32,<0.13.

Breaking changes

• Define build systems by default with uv init (#​19197)

  Projects created with uv init now declare a build system and are packaged by default. This was the default project layout all the way back in v0.3, but we found that the use of the hatchling build system was confusing to newcomers and consequently dropped use of a build system by default in v0.4. Since then, we've created our own build system (uv_build) with tight integration with uv and are excited to restore the default to a best-practice project layout.

  Previously, uv init example created an unpackaged layout containing main.py and a pyproject.toml without a build system. The project could declare dependencies but was not itself installed into its virtual environment.

  Now, uv init example defines a [build-system] using uv_build, places application source code in src/example, and includes a [project.scripts] entry named example. Defining a build system allows the project to be imported from tests or other code, installed as a dependency, and run as a command:

  $ uv init example
  $ cd example
  $ uv run example
  Hello from example!

  Existing projects are unaffected. Use uv init --no-package example to create the previous unpackaged layout without a build system.

  See the project creation documentation for more details.

  This stabilizes the packaged-init preview feature.

• Reject unsupported source distribution and wheel archive formats (#​18927)

  PEP 625 requires source distributions to use .tar.gz archives. Previously, uv also accepted legacy formats such as .tar.bz2 and .tar.xz. Those formats are now rejected, including when referenced by an existing lockfile. Legacy .zip source distributions remain supported for backwards compatibility.

  Wheels and other ZIP archives can no longer contain entries compressed with bzip2, LZMA, or XZ. Entries must use the stored, DEFLATE, or zstd compression methods.

  Removing support for uncommon compression methods reduces uv's compression dependencies and the attack surface exposed when processing untrusted packages.

  You cannot opt out of this behavior. If you depend on a legacy source distribution that uses an unsupported format, we recommend rebuilding it as a .tar.gz archive and regenerating any lockfile containing references to the legacy archive.

• Reject wheel files that could replace the Python interpreter (#​20748, #​20749)

  uv already rejected wheel entry points named python, but case variants such as Python were still accepted. On case-insensitive filesystems, including common macOS and Windows setups, these entry points could overwrite the virtual environment's interpreter.

  Wheels could also place interpreter files in their .data/scripts directory or in paths such as .data/data/bin/python, bypassing the entry-point check and replacing the interpreter during installation.

  uv now rejects case-insensitive variants of reserved interpreter names and wheel data files that would be installed over an interpreter. This includes names such as Python, python.py, and Python.exe, along with other reserved interpreter names and their versioned variants.

  You cannot opt out of these checks. Rename conflicting entry points or wheel data files and rebuild the affected wheel.

• Prefer stable releases before falling back to pre-releases (#​19993)

  A dependency can introduce a pre-release requirement after resolution starts. uv previously required each package's pre-release eligibility to be known before resolution began: the default if-necessary-or-explicit mode allowed them for direct requirements that explicitly requested a pre-release, or for packages that only published pre-releases.

  This meant that a pre-release requirement discovered in a dependency's metadata, e.g., example>=2.0.0b1, would fail to resolve even when a compatible pre-release existed. To resolve it, you had to add that dependency as a direct requirement or allow pre-releases across your entire dependency graph.

  The default mode is now if-necessary. uv tries stable candidates first and falls back to pre-releases when no stable candidate satisfies the active constraints. Like pip, uv now supports pre-release requirements discovered transitively, but can select different versions than previous uv releases when both stable and pre-release candidates are available.

  You can opt out of automatic pre-release selection with --prerelease disallow. Alternatively, --prerelease allow considers pre-releases without first preferring stable releases, and --prerelease explicit only allows them for direct requirements that mention a pre-release.

  The old if-necessary-or-explicit mode distinguished between explicitly requested pre-releases and packages with no stable releases. That distinction is unnecessary now that if-necessary handles both cases, including transitive requirements. The old name remains available as an alias but is deprecated and will be removed in a future release.

• Respect --require-hashes directives in requirements.txt (#​19336)

  Previously, uv pip install and uv pip sync warned about --require-hashes inside a requirements.txt file but still installed dependencies without checking their hashes. Now, the directive enables hash-checking mode, just as if --require-hashes had been passed on the command line.

  For example, this requirements file is no longer accepted because the requirement is neither pinned nor hashed:

  --require-hashes
  anyio
  

  You cannot opt out while the directive is present. Pin every requirement with == and provide its hash, or remove --require-hashes if hash checking is not intended.

• Reject MD5-only hashes in hash-checking mode (#​20758)

  Previously, uv pip install --require-hashes and uv pip sync --require-hashes accepted requirements whose only available digest used MD5. MD5 is not collision-resistant, so relying on it undermined installations that require hash verification and differed from pip's behavior.

  Hash-checking mode now requires at least one secure digest for every requirement. For example, the following requirement is rejected unless a secure hash, such as SHA-256, is also supplied:

  anyio==4.0.0 --hash=md5:420d85e19168705cdf0223621b18831a
  

  A secure hash can be supplied directly on the requirement or in a matching constraints file. Ordinary hash verification without --require-hashes continues to support MD5.

  You cannot opt out while hash checking is required. Regenerate affected hashes with SHA-256 or another supported secure hash.

• Reject invalid pylock.toml files and artifacts (#​20402, #​20440, #​20443)

  uv now validates additional requirements from the pylock.toml specification:

  • The packages array must be present. Previously, uv interpreted a missing array as an empty lockfile, so uv pip sync could uninstall an environment instead of rejecting malformed input. An explicitly empty packages = [] array remains valid.
  • Lockfile filenames must be pylock.toml or a single-name variant such as pylock.dev.toml. Names such as pylock..toml and pylock.foo.bar.toml are rejected.
  • If a wheel, source distribution, or other artifact declares a size, the downloaded or cached artifact must match. Previously, an incorrect size was accepted when the hash was correct. Sizes reported by package indexes remain advisory.

  You cannot opt out of these checks. Regenerate malformed lockfiles, rename invalid filenames, and either correct or remove an incorrect optional size value.

• Honor explicit certificate overrides even when no certificates can be loaded (#​20741, #​20767)

  Previously, uv ignored SSL_CERT_FILE or SSL_CERT_DIR values that pointed to missing or inaccessible paths, empty files or directories, or sources without valid certificates. Instead, it fell back to its default trust roots, potentially allowing HTTPS connections that the configured override was intended to reject.

  Now, any non-empty SSL_CERT_FILE or SSL_CERT_DIR value replaces uv's default certificate roots, even when no valid certificates can be loaded. In that case, HTTPS requests fail because no certificates are trusted. This applies to package downloads and remote scripts, including GitHub Gists.

  Fix or unset the certificate override. Unsetting it restores the default trust store; empty environment-variable values continue to be ignored.

• Support pip-compatible --cert handling in uv pip (#​20418)

  The uv pip interface now accepts --cert <path>, e.g.:

  $ uv pip install --cert ./company-ca.pem example

  As in pip, the provided PEM bundle replaces all other certificate sources for that invocation, including system certificates and SSL_CERT_FILE or SSL_CERT_DIR. This change has no effect unless you pass --cert. Include the necessary certificate authorities in the bundle.

  --cert is only supported by uv pip commands; other uv commands continue to use their existing certificate configuration.

• Discover projects relative to the script passed to uv run (#​20225)

  Previously, uv run project/script.py discovered its project from the current directory, even when the script belonged to another project. uv now starts project and workspace discovery from the script's directory instead.

  For example, running uv run other-project/script.py now uses other-project and its dependencies. This fixes scripts that previously failed because their own dependencies were not installed, but can select a different environment than before.

  You can opt out of script-relative discovery by selecting a project explicitly, e.g., uv run --project . other-project/script.py.

  This stabilizes the target-workspace-discovery preview feature.

• Require --force before clearing a directory that is not a virtual environment (#​20225)

  uv venv --clear previously removed any existing target directory, even if it was not a virtual environment. uv emitted a warning but still deleted the directory and its contents. Now, uv refuses to clear directories that do not contain a virtual environment.

  You can opt out of this safety check by explicitly passing --force, e.g., uv venv --clear --force ./not-a-virtualenv.

  This stabilizes the venv-safe-clear preview feature.

• Reject --project when initializing a project (#​20225)

  --project selects an existing project, so it is not meaningful when initializing a new one. Previously, uv init --project example warned and initialized example anyway; if a positional path was also provided, --project was ignored.

  This usage is now an error. Use uv init example to initialize a project at the requested path, or uv init --directory example to change the working directory first.

  This stabilizes the init-project-flag preview feature.

• Reject missing or invalid --project paths (#​20225)

  uv previously warned when --project referred to a missing directory or a file other than pyproject.toml, but then attempted to continue. This could produce confusing errors later or run against an unintended project.

  Now, uv run --project missing python fails immediately instead of continuing. You cannot opt out of this behavior. Create the directory first or select an existing project. Passing --project path/to/pyproject.toml remains supported and selects the file's parent directory.

  This stabilizes the project-directory-must-exist preview feature.

• Skip distributions with non-normalized filenames when publishing (#​20225)

  Distribution filenames must use normalized package names and versions. For example, a wheel for version 1.01.0 should be named example-1.1.0-py3-none-any.whl, not example-1.01.0-py3-none-any.whl.

  Previously, uv publish warned about non-normalized filenames but still attempted to upload them. It now skips the affected wheels and source distributions instead.

  You cannot opt out of this behavior. Rebuild distributions with normalized filenames before publishing.

  This stabilizes the publish-require-normalized preview feature.

• Classify Conda environments named base and root by their paths (#​20225)

  Conda environments named base or root were previously assumed to be the base Conda environment, even when they were ordinary child environments. uv now recognizes child Conda environments named base or root based on their paths, as it already does for other names.

  You can opt out of automatic interpreter selection by requesting an interpreter explicitly with --python /path/to/python.

  This stabilizes the special-conda-env-names preview feature.

• Reject broken .venv symlinks during environment discovery (#​20433)

  Previously, uv could ignore a broken .venv symlink and continue searching parent directories for another virtual environment. As a result, commands such as uv pip install could unexpectedly modify an unrelated ancestor environment.

  uv now stops at a broken .venv symlink and reports its exact path. Errors encountered while reading virtual environment metadata, including permission failures, are also reported immediately instead of being ignored.

  You cannot opt out of this behavior. Repair or remove the broken .venv symlink and correct any permissions that prevent uv from inspecting the environment.

• Reinstall matching installed Python patch versions instead of upgrading implicitly (#​20659)

  Before Python upgrades were supported, uv python install 3.12 --reinstall doubled as a way to install the latest Python 3.12 patch release. Now that --upgrade is available, --reinstall reinstalls the matching patch releases that are already present.

  For example, if Python 3.12.6 and 3.12.7 are installed, uv python install 3.12 --reinstall reinstalls both versions instead of installing the latest available 3.12 release.

  You can recover the previous upgrade behavior with uv python install 3.12 --upgrade. Combine --upgrade --reinstall to reinstall only the latest patch.

• Require --upgrade-group to name an existing dependency group (#​18957)

  Previously, uv lock --upgrade-group docs silently succeeded even if no docs dependency group existed. uv now validates the requested group against the project, its workspace members, and workspace-level dependency groups.

  You cannot opt out of this behavior. Correct the group name or add it to [dependency-groups]. Legacy tool.uv.dev-dependencies still satisfies --upgrade-group dev.

• Resolve relative indexes and find-links against --directory (#​20740)

  The --directory option changes the directory in which uv operates. Previously, relative index and find-links paths supplied on the command line were still resolved against the original working directory.

  uv now resolves --index, --default-index, --index-url, --extra-index-url, and --find-links relative to the directory selected by --directory. For example:

  $ uv add --directory project --index ./packages example

  This now uses project/packages instead of ./packages in the original working directory. Absolute paths and indexes loaded from configuration files are unaffected.

  To preserve the previous target, pass an absolute path or adjust the relative path, e.g., --index ../packages.

• Preserve absolute paths provided to uv add (#​18402)

  uv add previously converted every local dependency into a project-relative path, even when the original request used an absolute path or a literal file:// URL. It now preserves the form of the request in pyproject.toml and uv.lock:

  $ uv add ../library             # remains relative
  $ uv add /projects/library      # remains absolute

  Absolute paths make a project less portable. Use a relative path to avoid recording an absolute path. URLs containing expanded variables retain their existing relative-path behavior.

• Remove older PyPy distributions that are only available as bzip2 archives (#​20423)

  Older PyPy patch releases that are only distributed as .tar.bz2 archives are no longer available through uv python install. These releases require unsupported bzip2 archives.

  The latest PyPy release for each supported Python minor version is available as a gzip-compressed archive and remains supported. For example, uv python list 3.10 --all-versions still includes the latest PyPy 3.10 release, but older bzip2-only patch releases are omitted.

  You cannot opt out of this behavior. Request a newer PyPy patch release instead.

• Omit excluded-package comments when annotations are disabled (#​20085)

  uv pip compile --no-annotate suppresses comments describing the generated requirements file. Previously, a footer listing packages excluded with --unsafe-package was still included, even though annotations were disabled. That footer is now omitted.

  You can recover the footer by removing --no-annotate.

Stabilizations

• TOML 1.0-compatible source distributions (#​20225)

  uv_build now writes a TOML 1.0-compatible pyproject.toml when building source distributions, allowing older Python build frontends to consume projects that use newer TOML syntax. The original project file remains available in the archive as pyproject.toml.orig.

  This stabilizes the toml-backwards-compatibility preview feature.

• Automatic open-file limit adjustment on Unix (#​20225)

  On Linux and macOS, uv now attempts to raise the soft open-file limit at startup toward the hard limit, capped at 1,048,576 descriptors. The new limit also applies to subprocesses and reduces failures caused by running out of file descriptors. If the limit cannot be raised, uv continues running with the existing limit.

  This stabilizes the adjust-ulimit preview feature.

Preview features

• Allow uv upgrade to target multiple packages, upgrade all production dependencies, and exclude selected dependencies (#​20338)

Bug fixes

• Include extras activated by dependency groups when evaluating conflicts (#​20237)

v0.11.33

Compare Source

Released on 2026-07-28.

Enhancements

• Abort panics in release builds for smaller uv binaries (#​20271)
• Use .tar.gz archives for Pyodide installs (#​20667)

Preview features

• Avoid checking any scripts in uv check unless --script is passed (#​20676)
• Check locked tools for malware before cache reuse (#​20301)
• Write and read package.metadata-free lockfiles (#​20688, #​20691, #​20685, #​20695)

Bug fixes

• Correctly split dependencies into production and optional markers (#​20671)
• Fix discrepancies in argument parsing of exclude-newer (#​20679)
• Cleanup managed Python temporary directory on error (#​20752)

v0.11.32

Compare Source

Released on 2026-07-23.

Preview features

• Add --package and --all-packages selection to uv check (#​20628)
• Allow uv upgrade to update multiple marker-specific declarations of the same package (#​20335)
• Reject non-canonically formatted lockfiles in uv lock --check and commands using --locked (#​20646)
• Regenerate non-canonically formatted lockfiles with uv lock --refresh (#​20634)
• Include best-effort information about the active environment in uv workspace metadata by default (#​20643)

Performance

• Skip dependency-group conflict expansion when no additional conflicts can be inferred (#​20611)

Bug fixes

• Fork universal resolutions when Requires-Python is discovered only from distribution metadata (#​20586)

v0.11.31

Compare Source

Released on 2026-07-21.

Enhancements

• Allow workspace sources to reference members in another workspace by path (#​18401)
• Support .venv files containing paths to centralized project environments (#​20022)
• Update bundled Windows timezone data to IANA 2026c (#​20554)

Preview features

• Add an index-specific hash-algorithm setting for lockfile generation (#​20605)

Configuration

• Add audit.malware-check and audit.malware-check-url settings (#​20587)

Performance

• Avoid quadratic work when deduplicating transitive conflicts (#​20578)

Bug fixes

• Suggest --emit-build-options for unsupported uv pip compile --emit-options (#​20582)
• Reject source distributions and wheels with mismatched package names (#​20432)
• Avoid retrying TLS certificate verification failures (#​16245)
• Avoid warnings about uv_build settings for in-tree build backends (#​20153)

v0.11.30

Compare Source

Released on 2026-07-20.

Python

• Add CPython 3.15.0b4 (#​20519)

Preview features

• Allow uv workspace metadata --sync to target the active virtual environment with --active (#​20500)
• Reuse centralized project environments when workspaces are accessed through symlinks (#​20436)

Performance

• Skip resolver candidates whose files are all excluded by exclude-newer (#​20460)
• Limit parallel cache reads to reduce resolver scheduling and allocation overhead (#​20427)
• Accelerate lockfile serialization with toml_writer (#​20450)
• Compact cached Simple API distribution metadata and hashes (#​20463, #​20483)
• Decode stale cache entries in a single blocking task (#​20486)
• Decode cached payloads outside resolver workers (#​20464)
• Cache resolver Python requirement markers (#​20461)
• Reuse resolver fork markers while recording preferences (#​20462)

Bug fixes

• Prevent skipped tar-wheel entries from causing unrelated files to be removed during uninstall (#​20429)
• Preserve literal extends-environment paths in pyvenv.cfg on Unix (#​20466)

Documentation

• Add a contribution guide (#​20511, #​20552)

v0.11.29

Compare Source

Released on 2026-07-15.

Python

• Use gzip-compressed artifacts for PyPy downloads (#​20265)

Enhancements

• Add JSON output to uv tree (#​19978)
• Add CUDA 13.2 as a supported PyTorch backend (#​20267)
• Prefer local artifacts over URLs when installing from pylock.toml (#​20393)
• Clarify diagnostics for unsatisfiable direct requirement ranges (#​20227)
• Include the selected project name in missing-extra errors (#​20358)

Preview features

• Preserve extras and dependency-group conflict context when selecting locked project tools (#​20078)
• Split OSV audit queries that exceed the service's 1,000-package limit (#​20398)
• Apply OSV fixed-version information only to the matching package and ecosystem (#​20399)
• Skip the virtualenv distutils monkeypatch on Python 3.10 and later (#​20222)
• Report invalid uv audit --service-url values instead of panicking (#​20374)
• Include preview settings in the published SchemaStore schema (#​20304)

Performance

• Reduce resolver work by widening selected versions across ranges without other known candidates (#​20115)
• Defer client and build setup for no-op uv sync operations (#​20364)
• Reuse workspace discovery during frozen syncs (#​20363)
• Reuse workspace discovery after resolving settings (#​20356)
• Reuse workspace discovery in uv tree, uv export, uv format, and uv audit (#​20359)
• Avoid cache and interpreter setup when reading a project version (#​20360)

Bug fixes

• Reject duplicate active package entries in pylock.toml (#​20391)
• Preserve direct-archive hashes in uv pip freeze output (#​20395)
• Explain conflicting root requirements instead of displaying an empty version range (#​20228)
• Prevent build-backend data paths from escaping the project or bypassing wheel exclusions (#​20397)
• Reject PEP 517 backend paths outside the source tree, including paths that escape through symlinks (#​20387)
• Redact credentials from failed Git fetch commands (#​20401)
• Fix exclusive post-release range ordering to match PEP 440 (#​20268)
• Canonicalize equivalent PEP 440 ranges during dependency resolution (#​20182)
• Honor Python version pins when initializing scripts (#​20404)
• Respect package-scoped source filtering for scripts (#​20389)
• Report existing environment incompatibilities when uv pip install --strict has nothing to install (#​20388)
• Continue scanning platlib when purelib is missing (#​20405)
• Handle versionless .egg-info files as legacy package metadata (#​20403)
• Make repeated locking idempotent for impossible cross-variable platform markers (#​20369)
• Report invalid cloud credential endpoint URLs instead of panicking (#​20372)
• Report invalid pylock.toml artifact URLs instead of panicking (#​20373)
• Report non-UTF-8 virtual environment paths instead of panicking while generating activation scripts (#​20375)
• Return an unsupported-operation error from unimplemented build-backend requirement hooks (#​20376)

Documentation

• Clarify --no-build behavior for editable requirements (#​20234)
• Document uv's threat model (#​20236)
• Reduce the number of badges in the README (#​11257)

v0.11.28

Compare Source

Released on 2026-07-07.

Security

This release updates our ZIP library, astral-async-zip, to v0.0.20, which includes 15 changes that harden our ZIP handling against parser differentials. uv may reject ZIP archives with malformed or ambiguous content that were previously accepted.

See the upstream commits for a full list of changes.

Python

• Upgrade GraalPy to 25.1.3 (#​20069)

Enhancements

• Improve trace logs for unexpected error chains (#​20220)
• Move lockfile update guidance to a hint (#​20219)
• Preserve indentation for multiline error causes (#​20156)
• Render user errors with their cause chains (#​20217)
• Route final command errors through the printer to respect -q and -qq (#​20163)
• Use standard rendering for uv build errors (#​20159)
• Use standard rendering for tool requirement errors (#​20160)

Performance

• Only compile bytecode for installed distributions in uv pip install (#​19914)
• Avoid allocating URL-safe Git revisions (#​20194)
• Avoid allocating canonical Python request strings (#​20193)
• Avoid allocating custom Astral mirror URLs (#​20204)
• Avoid allocating expanded compatibility tags (#​20190)
• Avoid allocating shell strings that need no escaping (#​20196)
• Avoid allocating static ABI descriptions (#​20201)
• Avoid allocating static Windows executable names (#​20200)
• Avoid allocating static dependency table names (#​20199)
• Avoid allocating static platform triple components (#​20195)
• Avoid allocating static resolver report labels (#​20198)
• Avoid allocating static unavailable-version messages (#​20197)
• Avoid allocating unchanged Python download architectures (#​20202)
• Avoid allocating unchanged paths during case normalization (#​20203)
• Avoid allocations when expanding group conflicts (#​20211)
• Avoid allocations when formatting requirements (#​20206)
• Avoid cloning credential lookup services (#​20210)
• Avoid cloning dry-run distributions (#​20209)
• Avoid cloning owned dependency metadata (#​20212)
• Avoid redundant direct URL clones (#​20207)
• Create metadata version errors lazily (#​20205)
• Optimize expanded tag compatibility checks (#​20171)
• Optimize parsing of single-digit three-part versions (#​20118)

Bug fixes

• Avoid overflow when computing HTTP cache age (#​20178)
• Respect --upgrade when upgrade-package is configured (#​19955)
• Support uv tree in dependency-group-only projects (#​20167)
• Treat cache entries as stale at exact expiration (#​20183)

v0.11.27

Compare Source

Released on 2026-07-06.

Enhancements

• Continue on ignored errors when fetching wheel metadata (#​12255)
• Use caching for --python-downloads-json-url (#​16749)

Preview features

• Discover extensionless shebang scripts in uv workspace list --scripts (#​20099)

Performance

• Avoid full site-packages scans for direct reinstalls (#​20119)
• Avoid redundant pyproject parsing (#​20076)
• Cache default dependency markers when reading locks (#​20125)
• Enable SIMD-accelerated TOML parsing (#​20079)
• Intern requires-python specifiers in Simple API parsing (#​20104)
• Read cache entries into exact-sized buffers (#​20120)
• Reduce VersionSpecifiers parsing allocations (#​20105)
• Reduce site-packages scan allocation overhead (#​20087)
• Reuse package names when parsing wheel filenames (#​20110)
• Sort Simple API files after grouping (#​20112)

Bug fixes

• Always emit packages table for pylock.toml (#​20145)
• Avoid blank line for empty uv pip tree (#​20062)
• Encode hashes in file paths (#​19807)
• Error on a registry uv.lock package without a version instead of panicking (#​19855)
• Preserve conditional extra markers in exports (#​20148)
• Skip the ambiguous authority check for file transport VCS URLs (#​20086)
• Sync index format when uv add --index updates an existing index URL (#​19818)

Other changes

• Re-add pub APIs used in Pixi (#​20074)
• Update Rust toolchain to 1.96.1 (#​20103)

v0.11.26

Compare Source

Released on 2026-06-30.

Performance

• Adapt uv to IDs-only PubGrub dependencies (#​20048)
• Avoid allocations in ForkMap::contains (#​20023)
• Reuse resolver work across PubGrub iterations (#​20020)
• Speed up candidate selection for disjoint ranges (#​20026)

Bug fixes

• Warn when the build cache is inside the source directory (#​20056)

v0.11.25

Compare Source

Released on 2026-06-26.

Security

This release updates our tar library, astral-tokio-tar, to v0.6.3, which includes over 20 changes that harden our tar handling against parser differentials. uv may reject source distributions with malformed or ambiguous content that were previously accepted.

See the upstream commits for a full list of changes.

Enhancements

• Add a full "lockfile" to tool receipts (#​18937)
• Allow scoped overrides to add dependencies (#​19974)
• Avoid writing redundant lockfile markers with tool.uv.environments (#​19933)
• Factor supported environments out of lockfile markers (#​19969)
• Recommend our own build backend in the build frontend (#​19994)
• Reject wheels with multiple .dist-info directories (#​19986)
• Simplify dependency markers under parent reachability (#​19971)
• Support scoped dependency exclusions (#​19977)
• Support scoped dependency overrides (#​19970)
• Explain why files are skipped in registry index parsing (#​19983)

Preview features

• Add uv workspace list --scripts (#​20009)
• Support centralised environments in uv venv (#​19912)
• Use locked ty versions in uv check (#​19884)
• Add centralized storage of project environments (#​18214)
• Verify lockfile hashes before reusing a cached ty in uv check (#​19995)
• Use locked dependency selection for uv check --script (#​19989)

Bug fixes

• Preserve standalone markers in workspace metadata (#​20011)
• Reject uv build if the cache dir is enclosed (#​19991)

v0.11.24

Compare Source

Released on 2026-06-23.

Python

• Add CPython 3.15.0b3 (#​19964)

Preview features

• Make project environments relocatable under preview (#​19965)

Performance

• Use a compact index for lazy version maps (#​19959)

Bug fixes

• Allow disabling exclude-newer (#​19934)
• Avoid archive id collisions (#​19949)
• Reapply "Fix transparent Python upgrades in project environments" (#​19928)
• Clean up partial tool entrypoint installs (#​19966)
• Fix relocatable activate.fish and broaden Fish version support (#​19856)

v0.11.23

Compare Source

Released on 2026-06-19.

Bug fixes

• Revert "Fix transparent Python upgrades in project environments" to mitigate unintended breakage in pre-commit-uv (#​19925)
• Restore old behavior where workspace members "hidden" by an intermediate pyproject.toml would be treated as standalone projects (#​19926)

v0.11.22

Compare Source

Released on 2026-06-18.

Enhancements

• Publish wheels before sdists in uv publish (#​19831)
• Add TY and RUFF env vars for providing paths for binaries used by uv format and uv check (#​19821)

Preview features

• Allow configuring preview features in uv.toml and pyproject.toml (#​18437)
• Update the lockfile during uv check --no-sync (#​19909)
• Add --script to uv check and uv metadata (#​19860)
• Report workspace-exclusive dependency groups in workspace metadata (#​19862)
• Support SARIF as a uv audit output (#​19872)

Performance

• Use a more deadlock-resistant concurrent hashmap in the resolver (#​19532)

Bug fixes

• Update string marker ordering semantics to match upstream clarified rules (#​19808)
• Reject extras that have the same normalized name (#​19871)
• Reject dependency group include-group entries that have additional fields (#​19866)
• Reject invalid UTF-8 URL credentials (#​19814)
• Validate that PEP 517 backend-paths exist when building sdists (#​19834)
• Validate that pylock.toml files do not have an unsupported a lock-version (#​19869)
• Validate that the environment satisfies the packages.requires-python of a pylock.toml (#​19868)
• Allow uv to be recursively invoked by PEP 517 build hooks (#​19879)
• Allow empty credentials.toml files (#​19815)
• Fix transparent Python upgrades in project environments (#​19890)
• Handle non-file editable URLs in uv pip list (#​19867)
• Fix incorrect output from uv tree --invert (#​19910)
• Fix environment locking of uv venv in a project (#​19837)
• Fix handling of workspace-exclusive dependency groups in uv tree (#​19905)

Documentation

• Archive the 0.10.x changelog (#​19813)

Other changes

• Mark more tests as requiring network for vendors that need to run tests offline (#​19819)

v0.11.21

Compare Source

Released on 2026-06-11.

Python

• Add CPython 3.13.14 and 3.14.6 (#​19787)

Preview features

• Add environment.root to uv workspace metadata --sync (#​19760)
• Allow uv upgrade to update a single dependency constraint (#​19738)
• Compute and pass uv workspace metadata payload in ty check (#​19763)
• Make packaged applications the default for uv init (#​17841)

Performance

• Add parallel discovery of Python versions for uv python list (#​18684)
• Avoid normalizing source distribution names twice (#​19784)

Bug fixes

• Improve cache robustness and pruning behavior
  • Allow CI cache pruning without an sdist bucket (#​19802)
  • Avoid overflow when reading malformed cache entries (#​19799)
  • Preserve cached Python downloads during cache pruning (#​19795)
  • Reject running inside the cache (#​19659)
• Fix Python discovery and version request edge cases
  • Avoid panics for Unicode Python version requests (#​19797)
  • Fix handling of non-critical errors in uv python list with path requests (#​19774)
  • Fix stop-discovery-at regression (#​19769)
• Harden parsing and validation for package metadata, requirements, markers, URLs, and conflict sets
  • Allow trailing commas in version specifiers (#​19806)
  • Avoid panics for invalid UTF-8 URL credentials (#​19800)
  • Avoid panics for malformed source distribution filenames (#​19776)
  • Avoid panics for trailing extra separators (#​19779)
  • Avoid stack overflow for recursive requirements path aliases (#​19777)
  • Ignore reversed string compatible-release markers (#​19782)
  • Reject duplicate entries in conflict sets (#​19801)
  • Reject malformed hash options in requirements files (#​19783)
  • Reject source distribution filenames without a separator (#​19803)
  • Use UTF-8 lengths for requirement errors (#​19781)
  • Use UTF-8 lengths for trailing marker errors (#​19796)
  • Use byte offsets when peeking over requirements (#​19780)
  • Validate GraalPy ABI suffixes (#​19805)
• Improve wheel entry-point error handling and virtual environment activation quoting
  • Propagate errors when reading wheel entry points (#​19794)
  • Quote virtual environment activation paths with shell metacharacters (#​19798)

v0.11.20

Compare Source

Released on 2026-06-10.

Enhancements

• Add --emit-index-url and --emit-find-links to uv export (#​18370)
• Add --find-links support for uv pip list (#​16103)
• Group executable install errors during uv python install (#​19691)
• Use ICF in macOS release builds to reduce binary sizes (#​19615)

Preview features

• Add initial hidden uv upgrade command (#​19678)
• Reject Git revisions in uv upgrade (#​19742)

Configuration

• Recognize UV_NO_INSTALL_PROJECT, UV_NO_INSTALL_WORKSPACE, UV_NO_INSTALL_LOCAL (#​19323)

Performance

• Speed up discovery of large workspaces (#​18311)

Bug fixes

• Allow unknown preview flags with a warning again (#​19669)
• Apply dependency exclusions to direct requirements (#​19699)
• Avoid following external symlin

✂ Note

PR body was truncated to here.