chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.5 #79
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/ghcr-io-astral-sh-uv-0-x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.11.16-python3.14-alpine→0.12.5-python3.14-alpine0.11.16→0.12.5Release Notes
astral-sh/uv (ghcr.io/astral-sh/uv)
v0.12.5Compare Source
Released on 2026-08-14.
Python
Enhancements
Preview features
--indexand--default-indexto select configured package indexes by name with theindex-by-namepreview feature (#17455)cache-physical-spaceon filesystems that do not support physical-space accounting (#21133)Bug fixes
v0.12.4Compare Source
Released on 2026-08-13.
Enhancements
Requires-Python: >= 3.5.*(#21012)Preview features
uv check --no-install-projectand respectUV_NO_INSTALL_PROJECTto install dependencies without building or installing the project (#21085)uv checkhonor uv's color and progress settings, including quiet mode (#21086)Performance
Bug fixes
pythonw.exelaunchers for virtual environments created from managed Python minor-version links (#19235)uv lockto proceed when.venvis an unusable project environment (#21068)fork-strategywhen ordering forks created fromenvironmentsor existing lockfileresolution-markers(#21000)!=3.11.*, !=3.12.*inuv.lock(#21045)uv addupdates it (#21008)PYTHONEXECUTABLEand__PYVENV_LAUNCHER__overrides (#21075)uv version --bumpvalues (#21076)v0.12.3Compare Source
Released on 2026-08-07.
Python
Preview features
--output-formatto select automatic, human-readable, or raw-byte output foruv cache size(#20992)uv workspace metadata --quietwhile suppressing diagnostics (#20991)uv workspace metadataJSON output (#20990)Performance
Documentation
--python-pinto--pin-pythonin theuv init --bareexample (#20876)v0.12.2Compare Source
Released on 2026-08-05.
Python
Enhancements
Preview features
uv tool audit(#20921)cache-physical-spacepreview feature (#20925)Configuration
UV_RUN_RLIMIT_NOFILEto set the open-file limit for commands launched byuv run(#20926)Performance
uv.lockparsing for wheel entries (#20881)uv.lockparsing for source distribution entries (#20882)Bug fixes
Documentation
v0.12.1Compare Source
Released on 2026-07-31.
Enhancements
--prerelease-package(#20837)activate.xsh) (#19740)uv add --indexwhen updatingpyproject.toml(#20817)Preview features
uv checkwith--fix(#20793)uv check(#20742)Performance
Bug fixes
uv tool update-shellanduv python update-shellexit (#20842)--find-linkspaths in requirements files relative to the containing file (#20832)uv tool list --outdated(#20770)Documentation
v0.12.0Compare 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 onuv_build, update it to allowuv_build0.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 initnow 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 thehatchlingbuild 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 examplecreated an unpackaged layout containingmain.pyand apyproject.tomlwithout a build system. The project could declare dependencies but was not itself installed into its virtual environment.Now,
uv init exampledefines a[build-system]usinguv_build, places application source code insrc/example, and includes a[project.scripts]entry namedexample. Defining a build system allows the project to be imported from tests or other code, installed as a dependency, and run as a command:Existing projects are unaffected. Use
uv init --no-package exampleto create the previous unpackaged layout without a build system.See the project creation documentation for more details.
This stabilizes the
packaged-initpreview feature.Reject unsupported source distribution and wheel archive formats (#18927)
PEP 625 requires source distributions to use
.tar.gzarchives. Previously, uv also accepted legacy formats such as.tar.bz2and.tar.xz. Those formats are now rejected, including when referenced by an existing lockfile. Legacy.zipsource 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.gzarchive 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 asPythonwere 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/scriptsdirectory 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, andPython.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-explicitmode 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 allowconsiders pre-releases without first preferring stable releases, and--prerelease explicitonly allows them for direct requirements that mention a pre-release.The old
if-necessary-or-explicitmode distinguished between explicitly requested pre-releases and packages with no stable releases. That distinction is unnecessary now thatif-necessaryhandles 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-hashesdirectives inrequirements.txt(#19336)Previously,
uv pip installanduv pip syncwarned about--require-hashesinside arequirements.txtfile but still installed dependencies without checking their hashes. Now, the directive enables hash-checking mode, just as if--require-hasheshad been passed on the command line.For example, this requirements file is no longer accepted because the requirement is neither pinned nor hashed:
You cannot opt out while the directive is present. Pin every requirement with
==and provide its hash, or remove--require-hashesif hash checking is not intended.Reject MD5-only hashes in hash-checking mode (#20758)
Previously,
uv pip install --require-hashesanduv pip sync --require-hashesaccepted 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:
A secure hash can be supplied directly on the requirement or in a matching constraints file. Ordinary hash verification without
--require-hashescontinues 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.tomlfiles and artifacts (#20402, #20440, #20443)uv now validates additional requirements from the
pylock.tomlspecification:packagesarray must be present. Previously, uv interpreted a missing array as an empty lockfile, souv pip synccould uninstall an environment instead of rejecting malformed input. An explicitly emptypackages = []array remains valid.pylock.tomlor a single-name variant such aspylock.dev.toml. Names such aspylock..tomlandpylock.foo.bar.tomlare rejected.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
sizevalue.Honor explicit certificate overrides even when no certificates can be loaded (#20741, #20767)
Previously, uv ignored
SSL_CERT_FILEorSSL_CERT_DIRvalues 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_FILEorSSL_CERT_DIRvalue 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
--certhandling inuv pip(#20418)The
uv pipinterface now accepts--cert <path>, e.g.:As in pip, the provided PEM bundle replaces all other certificate sources for that invocation, including system certificates and
SSL_CERT_FILEorSSL_CERT_DIR. This change has no effect unless you pass--cert. Include the necessary certificate authorities in the bundle.--certis only supported byuv pipcommands; 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.pydiscovered 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.pynow usesother-projectand 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-discoverypreview feature.Require
--forcebefore clearing a directory that is not a virtual environment (#20225)uv venv --clearpreviously 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-clearpreview feature.Reject
--projectwhen initializing a project (#20225)--projectselects an existing project, so it is not meaningful when initializing a new one. Previously,uv init --project examplewarned and initializedexampleanyway; if a positional path was also provided,--projectwas ignored.This usage is now an error. Use
uv init exampleto initialize a project at the requested path, oruv init --directory exampleto change the working directory first.This stabilizes the
init-project-flagpreview feature.Reject missing or invalid
--projectpaths (#20225)uv previously warned when
--projectreferred to a missing directory or a file other thanpyproject.toml, but then attempted to continue. This could produce confusing errors later or run against an unintended project.Now,
uv run --project missing pythonfails 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.tomlremains supported and selects the file's parent directory.This stabilizes the
project-directory-must-existpreview 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.0should be namedexample-1.1.0-py3-none-any.whl, notexample-1.01.0-py3-none-any.whl.Previously,
uv publishwarned 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-normalizedpreview feature.Classify Conda environments named
baseandrootby their paths (#20225)Conda environments named
baseorrootwere previously assumed to be the base Conda environment, even when they were ordinary child environments. uv now recognizes child Conda environments namedbaseorrootbased 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-namespreview feature.Reject broken
.venvsymlinks during environment discovery (#20433)Previously, uv could ignore a broken
.venvsymlink and continue searching parent directories for another virtual environment. As a result, commands such asuv pip installcould unexpectedly modify an unrelated ancestor environment.uv now stops at a broken
.venvsymlink 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
.venvsymlink 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 --reinstalldoubled as a way to install the latest Python 3.12 patch release. Now that--upgradeis available,--reinstallreinstalls 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 --reinstallreinstalls 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 --reinstallto reinstall only the latest patch.Require
--upgrade-groupto name an existing dependency group (#18957)Previously,
uv lock --upgrade-group docssilently succeeded even if nodocsdependency 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]. Legacytool.uv.dev-dependenciesstill satisfies--upgrade-group dev.Resolve relative indexes and find-links against
--directory(#20740)The
--directoryoption 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-linksrelative to the directory selected by--directory. For example:This now uses
project/packagesinstead of./packagesin 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 addpreviously converted every local dependency into a project-relative path, even when the original request used an absolute path or a literalfile://URL. It now preserves the form of the request inpyproject.tomlanduv.lock: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.bz2archives are no longer available throughuv 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-versionsstill 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-annotatesuppresses comments describing the generated requirements file. Previously, a footer listing packages excluded with--unsafe-packagewas 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_buildnow writes a TOML 1.0-compatiblepyproject.tomlwhen 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 aspyproject.toml.orig.This stabilizes the
toml-backwards-compatibilitypreview 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-ulimitpreview feature.Preview features
uv upgradeto target multiple packages, upgrade all production dependencies, and exclude selected dependencies (#20338)Bug fixes
v0.11.33Compare Source
Release Notes
Released on 2026-07-28.
Enhancements
.tar.gzarchives for Pyodide installs (#20667)Preview features
uv checkunless--scriptis passed (#20676)package.metadata-free lockfiles (#20688, #20691, #20685, #20695)Bug fixes
Install uv 0.11.33
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.33
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.32Compare Source
Release Notes
Released on 2026-07-23.
Preview features
--packageand--all-packagesselection touv check(#20628)uv upgradeto update multiple marker-specific declarations of the same package (#20335)uv lock --checkand commands using--locked(#20646)uv lock --refresh(#20634)uv workspace metadataby default (#20643)Performance
Bug fixes
Requires-Pythonis discovered only from distribution metadata (#20586)Install uv 0.11.32
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.32
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.31Compare Source
Release Notes
Released on 2026-07-21.
Enhancements
.venvfiles containing paths to centralized project environments (#20022)Preview features
hash-algorithmsetting for lockfile generation (#20605)Configuration
audit.malware-checkandaudit.malware-check-urlsettings (#20587)Performance
Bug fixes
--emit-build-optionsfor unsupporteduv pip compile --emit-options(#20582)uv_buildsettings for in-tree build backends (#20153)Install uv 0.11.31
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.31
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.30Compare Source
Release Notes
Released on 2026-07-20.
Python
Preview features
uv workspace metadata --syncto target the active virtual environment with--active(#20500)Performance
exclude-newer(#20460)toml_writer(#20450)Bug fixes
extends-environmentpaths inpyvenv.cfgon Unix (#20466)Documentation
Install uv 0.11.30
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.30
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.29Compare Source
Release Notes
Released on 2026-07-15.
Python
Enhancements
uv tree(#19978)pylock.toml(#20393)Preview features
uv audit --service-urlvalues instead of panicking (#20374)Performance
uv syncoperations (#20364)uv tree,uv export,uv format, anduv audit(#20359)Bug fixes
pylock.toml(#20391)uv pip freezeoutput (#20395)uv pip install --stricthas nothing to install (#20388)platlibwhenpurelibis missing (#20405).egg-infofiles as legacy package metadata (#20403)pylock.tomlartifact URLs instead of panicking (#20373)Documentation
--no-buildbehavior for editable requirements (#20234)Install uv 0.11.29
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.29
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.28Compare Source
Release Notes
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
Enhancements
-qand-qq(#20163)uv builderrors (#20159)Performance
uv pip install(#19914)Bug fixes
--upgradewhenupgrade-packageis configured (#19955)uv treein dependency-group-only projects (#20167)Install uv 0.11.28
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.28
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.27Compare Source
Release Notes
Released on 2026-07-06.
Enhancements
--python-downloads-json-url(#16749)Preview features
uv workspace list --scripts(#20099)Performance
requires-pythonspecifiers in Simple API parsing (#20104)Bug fixes
packagestable for pylock.toml (#20145)uv pip tree(#20062)uv add --indexupdates an existing index URL (#19818)Other changes
pubAPIs used in Pixi (#20074)Install uv 0.11.27
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.27
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.26Compare Source
Release Notes
Released on 2026-06-30.
Performance
ForkMap::contains(#20023)Bug fixes
Install uv 0.11.26
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.26
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.25Compare Source
Release Notes
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
tool.uv.environments(#19933)Preview features
uv workspace list --scripts(#20009)uv venv(#19912)uv check(#19884)uv check(#19995)uv check --script(#19989)Bug fixes
uv buildif the cache dir is enclosed (#19991)Install uv 0.11.25
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.25
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.24Compare Source
Release Notes
Released on 2026-06-23.
Python
Preview features
Performance
Bug fixes
exclude-newer(#19934)activate.fishand broaden Fish version support (#19856)Install uv 0.11.24
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.24
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.23Compare Source
Release Notes
Released on 2026-06-19.
Bug fixes
pre-commit-uv(#19925)pyproject.tomlwould be treated as standalone projects (#19926)Install uv 0.11.23
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.23
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.22Compare Source
Release Notes
Released on 2026-06-18.
Enhancements
uv publish(#19831)TYandRUFFenv vars for providing paths for binaries used byuv formatanduv check(#19821)Preview features
uv.tomlandpyproject.toml(#18437)uv check --no-sync(#19909)--scripttouv checkanduv metadata(#19860)workspace metadata(#19862)uv auditoutput (#19872)Performance
Bug fixes
include-groupentries that have additional fields (#19866)backend-paths exist when building sdists (#19834)pylock.tomlfiles do not have an unsupported alock-version(#19869)packages.requires-pythonof apylock.toml(#19868)uvto be recursively invoked by PEP 517 build hooks (#19879)credentials.tomlfiles (#19815)uv pip list(#19867)uv tree --invert(#19910)uv venvin a project (#19837)uv tree(#19905)Documentation
Other changes
Install uv 0.11.22
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.22
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.21Compare Source
Release Notes
Released on 2026-06-11.
Python
Preview features
environment.roottouv workspace metadata --sync(#19760)uv upgradeto update a single dependency constraint (#19738)uv workspace metadatapayload inty check(#19763)uv init(#17841)Performance
uv python list(#18684)Bug fixes
uv python listwith path requests (#19774)Install uv 0.11.21
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.21
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.20Compare Source
Release Notes
Released on 2026-06-10.
Enhancements
--emit-index-urland--emit-find-linkstouv export(#18370)--find-linkssupport foruv pip list(#16103)uv python install(#19691)Preview features
uv upgradecommand (#19678)uv upgrade(#19742)Configuration
UV_NO_INSTALL_PROJECT,UV_NO_INSTALL_WORKSPACE,UV_NO_INSTALL_LOCAL(#19323)Performance
Bug fixes
VIRTUAL_ENVthroughcygpathinsidefishon Windows (#19703)Documentation
--find-linkscaching behavior (#19585)Install uv 0.11.20
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.20
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.19Compare Source
Release Notes
Released on 2026-06-03.
Python
Enhancements
Preview features
--isolatedinuv check(#19666)Bug fixes
Install uv 0.11.19
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.19
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.18Compare Source
Release Notes
Released on 2026-06-01.
Performance
Preview
uv checkto runtyfrom uv (#19605)Bug fixes
Other changes
Install uv 0.11.18
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.18
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.11.17Compare Source
Release Notes
Released on 2026-05-28.
Enhancements
uv addwith standard library modules (#19572)uv workspaceand itslistsubcommand in help output (#19533)ignore-error-codeswhen applicable (#19521)import-namesandimport-namespacessupport touv-build(PEP 794) (#19380)--no-editable-packageflag to various commands (#19584)uv toolinvocations (#19577)Preview features
uv workspace metadata(#19122)uv venv --clearto remove non-virtual environments (#19595)Bug fixes
tool.uv.conflicts(#19538)--env-fileinuv run(#19567)--check-url(#19594)--find-linksparsing (#19537)Documentation
Install uv 0.11.17
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.11.17
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate.
3c608e931422f4049b7echore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.25to chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.2622f4049b7e289b7d29cechore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.26to chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.27289b7d29cea2c5e1920echore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.27to chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.28a2c5e1920e22401262e8chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.28to chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.2922401262e8a86839fea9chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.29to chore(deps): update ghcr.io/astral-sh/uv docker taga86839fea9735ba24342chore(deps): update ghcr.io/astral-sh/uv docker tagto chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.30735ba243425e180ef2b8chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.30to chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.315e180ef2b8c74b3036bbchore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.31to chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.32c74b3036bbd0dc29764bchore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.32to chore(deps): update ghcr.io/astral-sh/uv docker tagd0dc29764b75391f9dd6chore(deps): update ghcr.io/astral-sh/uv docker tagto chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.3375391f9dd668389ed748chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.33to chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.068389ed748db4c051a53chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.0to chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.1db4c051a536df062a903chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.1to chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.26df062a903b633277593chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.2to chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.3b63327759340d769dbf6chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.3to chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.440d769dbf6e55a078295chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.4to chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.5View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.