NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #215 most downloaded on PyPI
An extremely fast Python package and project manager, written in Rust.
Latest stable
0.13.9
Last release 5 days ago
17 Nov 2026
Ships on a steady schedule
a new release about every 1 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
333 releases · first in 2024
Drag across the ruler to compare, or tap a release to open it.
Due to a permission error during publish to `crates.io`, this release was partially published and manually finished. Consequently, crates.io temporari
Released on 2025-11-24.
Due to a permission error during publish to crates.io, this release was partially published and manually finished. Consequently, crates.io temporarily did not include all of the artifacts and the GitHub Release was published by a maintainer instead of GitHub Actions. The artifacts from GitHub Actions were used without alteration. The GitHub release attestations for the artifacts are not available for this release.
--with-requirements to load extensionless inline-metadata scripts (#16744)uv publish (#16731)uv export from overwriting pyproject.toml (#16745)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.12/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.12/uv-installer.ps1 | iex"
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo astral-sh/uv
You can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Due to rate limiting during publish to `crates.io`, this release was partially published and manually finished. Consequently, crates.io temporarily di
Released on 2025-11-20.
Due to rate limiting during publish to crates.io, this release was partially published and manually finished. Consequently, crates.io temporarily did not include all of the artifacts and the GitHub Release was published by a maintainer instead of GitHub Actions. The artifacts from GitHub Actions were used without alteration. The GitHub release attestations for the artifacts are not available for this release.
See the python-build-standalone release notes for details.
uv init author serialization via toml_edit inline tables (#16778)pyproject.toml (#16734)always-authenticate when running under Dependabot (#16773)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.11/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.11/uv-installer.ps1 | iex"
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo astral-sh/uv
You can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>
Enforce UTF‑8-encoded license files during uv build
Released on 2025-11-17.
SSL_CERT_DIR (#16473)uv build (#16699)project.license-files glob matches nothing (#16697)pip install --target (and sync) install Python if necessary (#16694)python_downloads_json_url in pre-release Python version warnings (#16737)uv python --python-downloads-json-url (#16542)--upgrade in uv python install (#16676)python install --default for pre-release Python versions (#16706)uv workspace list to list workspace members (#16691)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.10/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.10/uv-installer.ps1 | iex"
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo astral-sh/uv
You can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>
Deprecate use of --project in uv init
Released on 2025-11-12.
--project in uv init (#16674)uv version --bump (#16555).rcdata to store metadata (#15068)--only-emit-workspace and similar variants to uv export (#16681)UV_NO_DEFAULT_GROUPS environment variable (#16645)torch-model-archiver and torch-tb-profiler from PyTorch backend (#16655)CMD path in FastAPI Dockerfile (#16701)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.9/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.9/uv-installer.ps1 | iex"
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo astral-sh/uv
You can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>
Accept multiple packages in uv export
Released on 2025-11-07.
uv export (#16603)uv sync (#16543)uv cache size command (#16032)+gil to require a GIL-enabled interpreter (#16537)uv init error for invalid directory names (#16554)uv build -h (#16632)UV_NO_GROUP as an environment variable (#16529)UV_NO_SOURCES as an environment variable (#15883)--check and --locked to be used together in uv lock (#16538)default-groups in schema (#16575)nvidia-smi (#15460)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.8/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.8/uv-installer.ps1 | iex"
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo astral-sh/uv
You can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>
Add Windows x86-32 emulation support to interpreter architecture checks
Released on 2025-10-30.
uv auth token output (#16504)--check flag (#16521)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.7/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.7/uv-installer.ps1 | iex"
This release contains an upgrade to Astral's fork of async_zip, which addresses potential sources of ZIP parsing differentials between uv and other Py
Released on 2025-10-29.
This release contains an upgrade to Astral's fork of async_zip, which addresses potential sources of ZIP parsing differentials between uv and other Python packaging tooling. See GHSA-pqhf-p39g-3x64 for additional details.
--clear to uv build to remove old build artifacts (#16371)--no-create-gitignore to uv build (#16369)pip install --system when externally managed (#16392)uv lock --check with outdated lockfile will print that --check was passed, instead of --locked (#16322)uv init template for Maturin (#16449)uv python upgrade (#16420)--find-links distributions (#16446)uv export --frozen when the lockfile is outdated (#16407)uv tree when --package is used with circular dependencies (#15908)pip freeze --quiet (#16491)uv auth login pyx.dev retries to 60s (#16498)uv add --group ... -r ... (#16490)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.6/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.6/uv-installer.ps1 | iex"
This release contains an upgrade to astral-tokio-tar, which addresses a vulnerability in tar extraction on malformed archives with mismatching size in…
Released on 2025-10-21.
This release contains an upgrade to astral-tokio-tar, which addresses a vulnerability in tar extraction on malformed archives with mismatching size information between the ustar header and PAX extensions. While the astral-tokio-tar advisory has been graded as "high" due its potential broader impact, the specific impact to uv is low due to a lack of novel attacker capability. Specifically, uv only processes tar archives from source distributions, which already possess the capability for full arbitrary code execution by design, meaning that an attacker gains no additional capabilities through astral-tokio-tar.
Regardless, we take the hypothetical risk of parser differentials very seriously. Out of an abundance of caution, we have assigned this upgrade an advisory: https://github.com/astral-sh/uv/security/advisories/GHSA-w476-p2h3-79g9
astral-tokio-tar to 0.5.6 to address a parsing differential (#16387)uv pip install failure if the --system flag is used to select an externally managed interpreter (#16318)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.5/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.5/uv-installer.ps1 | iex"
Add auto-detection for Intel GPU on Windows
Released on 2025-10-17.
uv auth token output (#16345)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.4/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.4/uv-installer.ps1 | iex"
Obfuscate secret token values in logs
Released on 2025-10-14.
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.3/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.3/uv-installer.ps1 | iex"
Avoid inferring check URLs for pyx in uv publish
Released on 2025-10-10.
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.2/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.2/uv-installer.ps1 | iex"
Fix pylock.toml config conflict error messages
Released on 2025-10-09.
UV_UPLOAD_HTTP_TIMEOUT and respect UV_HTTP_TIMEOUT in uploads (#16040)UV_WORKING_DIRECTORY for setting --directory (#16125)Scripts directory (#16206)requires-python (#15927)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.1/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.1/uv-installer.ps1 | iex"
This breaking release is primarily motivated by the release of Python 3.14, which contains some breaking changes (we recommend reading the "What's new…
Released on 2025-10-07.
This breaking release is primarily motivated by the release of Python 3.14, which contains some breaking changes (we recommend reading the "What's new in Python 3.14" page). uv may use Python 3.14 in cases where it previously used 3.13, e.g., if you have not pinned your Python version and do not have any Python versions installed on your machine. While we think this is uncommon, we prefer to be cautious. We've included some additional small changes that could break workflows.
See our Python 3.14 blog post for some discussion of features we're excited about!
There are no breaking changes to uv_build. If you have an upper bound in your [build-system] table, you should update it.
Python 3.14 is now the default stable version
The default Python version has changed from 3.13 to 3.14. This applies to Python version installation when no Python version is requested, e.g., uv python install. By default, uv will use the system Python version if present, so this may not cause changes to general use of uv. For example, if Python 3.13 is installed already, then uv venv will use that version. If no Python versions are installed on a machine and automatic downloads are enabled, uv will now use 3.14 instead of 3.13, e.g., for uv venv or uvx python. This change will not affect users who are using a .python-version file to pin to a specific Python version.
Allow use of free-threaded variants in Python 3.14+ without explicit opt-in (#16142)
Previously, free-threaded variants of Python were considered experimental and required explicit opt-in (i.e., with 3.14t) for usage. Now uv will allow use of free-threaded Python 3.14+ interpreters without explicit selection. The GIL-enabled build of Python will still be preferred, e.g., when performing an installation with uv python install 3.14. However, e.g., if a free-threaded interpreter comes before a GIL-enabled build on the PATH, it will be used. This change does not apply to free-threaded Python 3.13 interpreters, which will continue to require opt-in.
Use Python 3.14 stable Docker images (#16150)
Previously, the Python 3.14 images had an -rc suffix, e.g., python:3.14-rc-alpine or
python:3.14-rc-trixie. Now, the -rc suffix has been removed to match the stable
upstream images. The -rc images tags will no longer be
updated. This change should not break existing workflows.
Upgrade Alpine Docker image to Alpine 3.22
Previously, the uv:alpine Docker image was based on Alpine 3.21. Now, this image is based on Alpine 3.22. The previous image can be recovered with uv:alpine3.21 and will continue to be updated until a future release.
Upgrade Debian Docker images to Debian 13 "Trixie"
Previously, the uv:debian and uv:debian-slim Docker images were based on Debian 12 "Bookworm". Now, these images are based on Debian 13 "Trixie". The previous images can be recovered with uv:bookworm and uv:bookworm-slim and will continue to be updated until a future release.
Fix incorrect output path when a trailing / is used in uv build (#15133)
When using uv build in a workspace, the artifacts are intended to be written to a dist directory in the workspace root. A bug caused workspace root determination to fail when the input path included a trailing / causing the dist directory to be placed in the child directory. This bug has been fixed in this release. For example, uv build child/ is used, the output path will now be in <workspace root>/dist/ rather than <workspace root>/child/dist/.
uv python upgrade / install output when there is a no-op for one request (#16158)uv tool upgrade can’t move the tool (#16081)uv python upgrade requests (#16160)uv python upgrade replacement of installed binaries on pre-release to stable (#16159)uv pip compile args in layout.md (#16155)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.9.0/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.0/uv-installer.ps1 | iex"
Emit a message on cache clean and prune when lock is held
Released on 2025-10-06.
cache clean and prune when lock is held (#16138)--force flag for uv cache prune (#16137)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.24/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.24/uv-installer.ps1 | iex"
Build s390x on stable Rust compiler version
Released on 2025-10-03.
s390x on stable Rust compiler version (#16082)UV_SKIP_WHEEL_FILENAME_CHECK to allow installing invalid wheels (#16046)--no-sources (#16094)--no-color on the CLI (#16044)uv pip tree output (#16078)_CONDA_ROOT in reference (#16114)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.23/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.23/uv-installer.ps1 | iex"
Upgrade astral-tokio-tar to 0.5.5 which hardens tar archive extraction
Released on 2025-09-23.
astral-tokio-tar to 0.5.5 which hardens tar archive extraction (#16004)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.22/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.22/uv-installer.ps1 | iex"
Refresh lockfile when --refresh is provided
+Released on 2025-09-23.
--refresh is provided (#15994)Add support for S3 request signing (#15925)
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.21/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.21/uv-installer.ps1 | iex"
Add --force flag for uv cache clean
Released on 2025-09-22.
--force flag for uv cache clean (#15992)freethreaded+debug Python downloads in uv python list (#15985)uv run and uvx (#15990)package level conflicts to the conflicting dependencies docs (#15963)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.20/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.20/uv-installer.ps1 | iex"
See the python-build-standalone release notes for more details.
Released on 2025-09-19.
See the python-build-standalone release notes for more details.
uv cache clean parallel process safe (#15888)platform_machine marker for win_arm64 platform tag (#15921)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.19/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.19/uv-installer.ps1 | iex"
Deprecate tool.uv.dev-dependencies
Released on 2025-09-17.
uv init defaults for native build backend cache keys (#15705)pyproject.toml target does not exist for dependency groups (#15831)--no-clear to uv venv to disable removal prompts (#15795)--only-group and --extra flags (#15788)[project] to be missing from a pyproject.toml (#14113)base and root as base environments (#15682)uv_build is skipped (#15898)_CONDA_ROOT to detect Conda base environments (#15680)uv publish upload form (#15794)uv sync (#15881)tool.uv.dev-dependencies (#15469)native-auth feature (#15872)uv sync --no-sources not switching from editable to registry installations (#15234)@latest (#15827)triton as a torch backend package (#15910)UV_INSECURE_NO_ZIP_VALIDATION=1 in duplicate header errors (#15912)NO_PROXY support (#15816)requires-python (#14282)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.18/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.18/uv-installer.ps1 | iex"
Improve error message for HTTP validation in auth services
Released on 2025-09-10.
PYX_API_URL when suggesting uv auth login on 401 (#15774)uv init --script (#15747)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.17/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.17/uv-installer.ps1 | iex"
Due to a bug in the release process for the new loongarch64 support (see #15762), this release was partially published and manually finished. Conseque
Due to a bug in the release process for the new loongarch64 support (see #15762), this release was partially published and manually finished. Consequently, the uv_build artifacts were uploaded to PyPI with a PAT instead of via OIDC and the GitHub Release was published by a maintainer instead of GitHub Actions. The artifacts from GitHub Actions were used without alteration. The uv artifacts were not affected. There should be no consequences from this; we just want to be transparent about the provenance of the artifacts.
--editable to override editable = false annotations (#15712)editable = false for workspace sources (#15708)--with-requirements and --requirements (#12763)match-runtime target is optional (#15671)uv auth (#15743)uv publish (#15759)uv auth commands take a URL (#15664)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.16/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.16/uv-installer.ps1 | iex"
Upgrade SQLite 3.50.4 in CPython builds for CVE-2025-6965 (see also python/cpython#137134)
uv auth commands for credential management (#15570)uv auth commands (#15636)uv tree --show-sizes to show package sizes (#15531)--python-platform riscv64-unknown-linux (#15630)--python-platform to uv run and uv tool (#15515)uv publish --dry-run (#15638)extra-build-dependencies (#15622)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.15/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.15/uv-installer.ps1 | iex"
Add managed CPython distributions for aarch64 musl
--python-platform to uv pip check (#15486)UV_ISOLATED (#15428)--no-install-local option to uv sync, uv add and uv export (#15328)uv pip CLI (#15453){version} on uv format failure (#15527)uv format to prevent races (#15551)--project in uv format (#15438)uv format in the project root (#15440)WHEEL and METADATA reads in installed distributions (#15489)venv in current working directory (#15537)uv publish checks (#15545)uv venv (#15538)CLICOLOR_FORCE=1 when calling build backends (#15472)uvw.exe needs to be removed (#15536)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.14/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.14/uv-installer.ps1 | iex"
Add --no-install-* arguments to uv add
--no-install-* arguments to uv add (#15375)uv init (#15377)uv format command (#15017)extra-build-dependencies if match-runtime is explicitly false (#15420)triton to torch-backend manifest (#15405)uv_build wheel hashes (#15400)--upgrade-package on the command-line as overriding upgrade = false in configuration (#15395)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.13/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.13/uv-installer.ps1 | iex"
Improve performance of zstd in Python 3.14
See the python-build-standalone release notes for details.
aarch64-pc-windows-msvc target for python-platform (#15347)uv tool update-shell (#15356)buildpack-deps:trixie, debian:trixie-slim, alpine:3.22 (#15351)match-runtime = true for dynamic packages (#15292)uv cache clean instead of clear (#15313)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.12/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.12/uv-installer.ps1 | iex"
Add Debian 13 trixie to published Docker images
extra-build-dependencies hint for any missing module on build failure (#15252)reqwest clients to RegistryClient (#15281)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.11/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.11/uv-installer.ps1 | iex"
Add support for installing Pyodide versions
aarch64 (#14399)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.10/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.10/uv-installer.ps1 | iex"
Add --reinstall flag to uv python upgrade
--reinstall flag to uv python upgrade (#15194)uv python upgrade if they don't already exist (#15192)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.9/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.9/uv-installer.ps1 | iex"
Fix find_uv_bin compatibility with Python <3.10
find_uv_bin compatibility with Python <3.10 (#15177)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.8/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.8/uv-installer.ps1 | iex"
Tix is no longer provided on Linux. This is a deprecated Tk extension that appears to have been previously broken.
tkagg backend (the default on Linux), Pillow's PIL.ImageTk library, and other extension modules that need to use libtcl/libtk directly.See the python-build-standalone release notes for details.
uv.lock when using --isolated (#15154)--prefix and --with installations in find_uv_bin (#14184)find_uv_bin (#14181)find_uv_bin (#14182)package-level conflicts in workspaces (#14906)UV_DEV and UV_NO_DEV environment variables (for --dev and --no-dev) (#15010)--require-hashes applied to build dependencies in uv pip install (#15153)find_uv_bin (#14191).) to list elements in Features docs page (#15138)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.7/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.7/uv-installer.ps1 | iex"
This release contains hardening measures to address differentials in behavior between uv and Python's built-in ZIP parsers (CVE-2025-54368).
This release contains hardening measures to address differentials in behavior between uv and Python's built-in ZIP parsers (CVE-2025-54368).
Prior to this release, attackers could construct ZIP files that would be extracted differently by pip, uv, and other tools. As a result, ZIPs could be constructed that would be considered harmless by (e.g.) scanners, but contain a malicious payload when extracted by uv. As of v0.8.6, uv now applies additional checks to reject such ZIPs.
Thanks to a triage effort with the Python Security Response Team and PyPI maintainers, we were able to determine that these differentials were not exploited via PyPI during the time they were present. The PyPI team has also implemented similar checks and now guards against these parsing differentials on upload.
Although the practical risk of exploitation is low, we take the hypothetical risk of parser differentials very seriously. Out of an abundance of caution, we have assigned this advisory a CVE identifier and have given it a "moderate" severity suggestion.
These changes have been validated against the top 15,000 PyPI packages; however, it's plausible that a non-malicious ZIP could be falsely rejected with this additional hardening. As an escape hatch, users who do encounter breaking changes can enable UV_INSECURE_NO_ZIP_VALIDATION to restore the previous behavior. If you encounter such a rejection, please file an issue in uv and to the upstream package.
For additional information, please refer to the following blog posts:
UV_HTTP_RETRIES in uv publish (#15106)UV_NO_EDITABLE where --no-editable is supported (#15107)cargo-dist to add UV_INSTALLER_URL to PowerShell installer (#15114)h2 again to avoid too_many_internal_resets errors (#15111)pythonw when copying entry points in uv run (#15134)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.6/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.6/uv-installer.ps1 | iex"
Enable uv run with a GitHub Gist
uv run with a GitHub Gist (#15058)uv tool install (#14014)extra-build-dependencies warnings for uv pip (#15088)pylock warning (#15089)python-preference = system when managed interpreters are on the PATH (#15059)--system is used (#15061)h2 upgrade (#15079)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.5/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.5/uv-installer.ps1 | iex"
Improve styling of warning cause chains
extra-build-dependencies (#14735)exclude-newer dates via exclude-newer-package (#14489)python vs python3 (#14970)environments and required-environments in uv.toml (#14905)uv_build in projects documentation (#14968)UV_ prefix to installer environment variables (#14964)uv from --build-backend options (#14939)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.4/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.4/uv-installer.ps1 | iex"
See the `python-build-standalone` release notes for more details.
See the python-build-standalone release notes for more details.
--with versions over base environment versions (#14863)uv_build reference documentation (#14853)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.3/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.3/uv-installer.ps1 | iex"
Add derivation chains for dependency errors
UV_INIT_BUILD_BACKEND (#14821)tls_built_in_root_certs for client (#14816)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.2/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.2/uv-installer.ps1 | iex"
Allow --config-settings-package to apply configuration settings at the package level
HF_TOKEN (#14797)--config-settings-package to apply configuration settings at the package level (#14573)python3.13t executables in uv venv (#14764)python -m uv in interrupted with Ctrl-C on Windows (#14715)--bounds formatting for uv_build bounds in uv init (#14731)extras and dependency_groups markers in PEP 508 grammar (#14753)extras and dependency_groups markers on uv pip install and uv pip sync (#14755)uv self version when uv version cannot find a project (#14738)[tool.uv] fields more precise (#14325)uv sync with --quiet (#14810)Cache-Control overrides to response, not request headers (#14736)requires-python in pylock.toml (#14787)README variants in build backend (#14762)pyvenv.cfg last (#14808)dependency-metadata (#14801)setup-uv after setup-python in Github Actions integration guide (#14741)requires-python behavior are consistent with pip (#14752)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.1/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.1/uv-installer.ps1 | iex"
Since we released uv 0.7.0 in April, we've accumulated various changes that improve correctness and user experience, but could break some workflows. T
Since we released uv 0.7.0 in April, we've accumulated various changes that improve correctness and user experience, 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.
This release also includes the stabilization of a couple uv python install features, which have been available under preview since late last year.
Install Python executables into a directory on the PATH (#14626)
uv python install now installs a versioned Python executable (e.g., python3.13) into a directory on the PATH (e.g., ~/.local/bin) by default. This behavior has been available under the --preview flag since Oct 2024. This change should not be breaking unless it shadows a Python executable elsewhere on the PATH.
To install unversioned executables, i.e., python3 and python, use the --default flag. The --default flag has also been in preview, but is not stabilized in this release.
Note that these executables point to the base Python installation and only include the standard library. That means they will not include dependencies from your current project (use uv run python instead) and you cannot install packages into their environment (use uvx --with <package> python instead).
As with tool installation, the target directory respects common variables like XDG_BIN_HOME and can be overridden with a UV_PYTHON_BIN_DIR variable.
You can opt out of this behavior with uv python install --no-bin or UV_PYTHON_INSTALL_BIN=0.
See the documentation on installing Python executables for more details.
Register Python versions with the Windows Registry (#14625)
uv python install now registers the installed Python version with the Windows Registry as specified by PEP 514. This allows using uv installed Python versions via the py launcher. This behavior has been available under the --preview flag since Jan 2025. This change should not be breaking, as using the uv Python versions with py requires explicit opt in.
You can opt out of this behavior with uv python install --no-registry or UV_PYTHON_INSTALL_REGISTRY=0.
Prompt before removing an existing directory in uv venv (#14309)
Previously, uv venv would remove an existing virtual environment without confirmation. While this is consistent with the behavior of project commands (e.g., uv sync), it's surprising to users that are using imperative workflows (i.e., uv pip). Now, uv venv will prompt for confirmation before removing an existing virtual environment. If not in an interactive context, uv will still remove the virtual environment for backwards compatibility. However, this behavior is likely to change in a future release.
The behavior for other commands (e.g., uv sync) is unchanged.
You can opt out of this behavior by setting UV_VENV_CLEAR=1 or passing the --clear flag.
Validate that discovered interpreters meet the Python preference (#7934)
uv allows opting out of its managed Python versions with the --no-managed-python and python-preference options.
Previously, uv would not enforce this option for Python interpreters discovered on the PATH. For example, if a symlink to a managed Python interpreter was created, uv would allow it to be used even if --no-managed-python was provided. Now, uv ignores Python interpreters that do not match the Python preference unless they are in an active virtual environment or are explicitly requested, e.g., with --python /path/to/python3.13.
Similarly, uv would previously not invalidate existing project environments if they did not match the Python preference. Now, uv will invalidate and recreate project environments when the Python preference changes.
You can opt out of this behavior by providing the explicit path to the Python interpreter providing --managed-python / --no-managed-python matching the interpreter you want.
Install dependencies without build systems when they are path sources (#14413)
When working on a project, uv uses the presence of a build system to determine if it should be built and installed into the environment. However, when a project is a dependency of another project, it can be surprising for the dependency to be missing from the environment.
Previously, uv would not build and install dependencies with path sources unless they declared a build system or set tool.uv.package = true. Now, dependencies with path sources are built and installed regardless of the presence of a build system. If a build system is not present, the setuptools.build_meta:__legacy__ backend will be used (per PEP 517).
You can opt out of this behavior by setting package = false in the source declaration, e.g.:
[tool.uv.sources]
foo = { path = "./foo", package = false }
Or, by setting tool.uv.package = false in the dependent pyproject.toml.
See the documentation on virtual dependencies for details.
Install dependencies without build systems when they are workspace members (#14663)
As described above for dependencies with path sources, uv previously would not build and install workspace members that did not declare a build system. Now, uv will build and install workspace members that are a dependency of another workspace member regardless of the presence of a build system. The behavior is unchanged for workspace members that are not included in the project.dependencies, project.optional-dependencies, or dependency-groups tables of another workspace member.
You can opt out of this behavior by setting tool.uv.package = false in the workspace member's pyproject.toml.
See the documentation on virtual dependencies for details.
Bump --python-platform linux to manylinux_2_28 (#14300)
uv allows performing platform-specific resolution for explicit targets and provides short aliases, e.g., linux, for common targets.
Previously, the default target for --python-platform linux was manylinux_2_17, which is compatible with most Linux distributions from 2014 or newer. We now default to manylinux_2_28, which is compatible with most Linux distributions from 2019 or newer. This change follows the lead of other tools, such as cibuildwheel, which changed their default to manylinux_2_28 in Mar 2025.
This change only affects users requesting a specific target platform. Otherwise, uv detects the manylinux target from your local glibc version.
You can opt out of this behavior by using --python-platform x86_64-manylinux_2_17 instead.
Remove uv version fallback (#14161)
In Apr 2025, uv changed the uv version command to an interface for viewing and updating the version of the current project. However, when outside a project, uv version would continue to display uv's version for backwards compatibility. Now, when used outside of a project, uv version will fail.
You cannot opt out of this behavior. Use uv self version instead.
Require --global for removal of the global Python pin (#14169)
Previously, uv python pin --rm would allow you to remove the global Python pin without opt in. Now, uv requires the --global flag to remove the global Python pin.
You cannot opt out of this behavior. Use the --global flag instead.
Support conflicting editable settings across groups (#14197)
Previously, uv would always treat a package as editable if any requirement requested it as editable. However, this prevented users from declaring path sources that toggled the editable setting across dependency groups. Now, uv allows declaring different editable values for conflicting groups. However, if a project includes a path dependency twice, once with editable = true and once without any editable annotation, those are now considered conflicting, and uv will exit with an error.
You cannot opt out of this behavior. Use consistent editable settings or mark groups as conflicting.
Make uv_build the default build backend in uv init (#14661)
The uv build backend (uv_build) was stabilized in uv 0.7.19. Now, it is the default build backend for uv init --package and uv init --lib. Previously, hatchling was the default build backend. A build backend is still not used without opt-in in uv init, but we expect to change this in a future release.
You can opt out of this behavior with uv init --build-backend hatchling.
Set default UV_TOOL_BIN_DIR on Docker images (#13391)
Previously, UV_TOOL_BIN_DIR was not set in Docker images which meant that uv tool install did not install tools into a directory on the PATH without additional configuration. Now, UV_TOOL_BIN_DIR is set to /usr/local/bin in all Docker derived images.
When the default image user is overridden (e.g. USER <UID>) with a less privileged user, this may cause uv tool install to fail.
You can opt out of this behavior by setting an alternative UV_TOOL_BIN_DIR.
Update --check to return an exit code of 1 (#14167)
uv uses an exit code of 1 to indicate a "successful failure" and an exit code of 2 to indicate an "error".
Previously, uv lock --check and uv sync --check would exit with a code of 2 when the lockfile or environment were outdated. Now, uv will exit with a code of 1.
You cannot opt out of this behavior.
Use an ephemeral environment for uv run --with invocations (#14447)
When using uv run --with, uv layers the requirements requested using --with into another virtual environment and caches it. Previously, uv would invoke the Python interpreter in this layered environment. However, this allows poisoning the cached environment and introduces race conditions for concurrent invocations. Now, uv will layer another empty virtual environment on top of the cached environment and invoke the Python interpreter there. This should only cause breakage in cases where the environment is being inspected at runtime.
You cannot opt out of this behavior.
Restructure the uv venv command output and exit codes (#14546)
Previously, uv used miette to format the uv venv output. However, this was inconsistent with most of the uv CLI. Now, the output is a little different and the exit code has switched from 1 to 2 for some error cases.
You cannot opt out of this behavior.
Default to --workspace when adding subdirectories (#14529)
When using uv add to add a subdirectory in a workspace, uv now defaults to adding the target as a workspace member.
You can opt out of this behavior by providing --no-workspace.
Add missing validations for disallowed uv.toml fields (#14322)
uv does not allow some settings in the uv.toml. Previously, some settings were silently ignored when present in the uv.toml. Now, uv will error.
You cannot opt out of this behavior. Use --no-config or remove the invalid settings.
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.0/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.0/uv-installer.ps1 | iex"
See the GraalPy release notes for more details.
See the GraalPy release notes for more details.
UV_COMPILE_BYTECODE_TIMEOUT environment variable (#14369)cache-control headers (#14620)UV_LIBC to override libc selection in multi-libc environment (#14646)--all-arches when paired with --only-downloads (#14629)uv.toml when provided via direct path (#14653)revision in the lockfile versioning doc (#14634)uv cache clean prior to --reinstall (#14659)uv python update-shell (#14627)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.22/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.22/uv-installer.ps1 | iex"
Restore the SQLite fts4, fts5, rtree, and geopoly extensions on macOS and Linux
fts4, fts5, rtree, and geopoly extensions on macOS and LinuxSee the python-build-standalone release notes for more details.
--python-platform to uv sync (#14320)uv version --bump (#13578)-w shorthand for --with (#14530)UV_HTTP_RETRIES to customize retry counts (#14544)cache-key (#13438)..) in globs in cache-key (#13469)cache-key performance (#13469)uv sync --output-format json (#13689)uv tool if it is incompatible with --python (#14606)include-group (#14539)setup-python (#14533)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.21/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.21/uv-installer.ps1 | iex"
Add zstd support to Python 3.14 on Unix (it already was available on Windows)
See the PyPy and python-build-standalone release notes for more details.
--workspace flag to uv add (#14496)uv version (#14434)uv-extract to enable retries (#14450)NoSolutionError (#14457)ErrorTree for NoSolutionError public (#14444)cache-dependency-glob examples for setup-uv (#14493)uv pip sync suggestion with pyproject.toml (#14510)setup-uv@v6 (#14490)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.20/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.20/uv-installer.ps1 | iex"
The [uv build backend](https://docs.astral.sh/uv/concepts/build-backend/) is now stable, and considered ready for production use.
The uv build backend is now stable, and considered ready for production use.
The uv build backend is a great choice for pure Python projects. It has reasonable defaults, with the goal of requiring zero configuration for most users, but provides flexible configuration to accommodate most Python project structures. It integrates tightly with uv, to improve messaging and user experience. It validates project metadata and structures, preventing common mistakes. And, finally, it's very fast — uv sync on a new project (from uv init) is 10-30x faster than with other build backends.
To use uv as a build backend in an existing project, add uv_build to the [build-system] section in your pyproject.toml:
[build-system]
requires = ["uv_build>=0.7.19,<0.8.0"]
build-backend = "uv_build"
In a future release, it will replace hatchling as the default in uv init. As before, uv will remain compatible with all standards-compliant build backends.
See the python-build-standalone release for more details.
--universal pip compile (#14405)sys.prefix in cached environment keys to avoid --with collisions across projects (#14403)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.19/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.19/uv-installer.ps1 | iex"
Added arm64 Windows Python 3.11, 3.12, 3.13, and 3.14
Added arm64 Windows Python 3.11, 3.12, 3.13, and 3.14
These are not downloaded by default, since x86-64 Python has broader ecosystem support on Windows.
However, they can be requested with cpython-<version>-windows-aarch64.
ManagedPythonDownload::fetch_with_retry (#14378)python_version and python_full_version (#14271)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.18/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.18/uv-installer.ps1 | iex"
Apply build constraints when resolving --with dependencies
--with dependencies (#14340)UV_PYTHON_CACHE_DIR when empty (#14336)pyvenv.cfg version conflict (#14329)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.17/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.17/uv-installer.ps1 | iex"
See the `python-build-standalone` release notes for more details.
See the python-build-standalone release notes for more details.
~= is used as a Python version specifier without a patch version (#14008)requirements.txt (#14288)/simple component (#14251)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.16/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.16/uv-installer.ps1 | iex"
Consistently use Ordering::Relaxed for standalone atomic use cases
Ordering::Relaxed for standalone atomic use cases (#14190)--index (#14152)schema.json descriptions (#13693)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.15/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.15/uv-installer.ps1 | iex"
Add ROCm backends to --torch-backend
--torch-backend (#14172)--torch-backend (#14120)--torch-backend (#14119)[tool.uv.dependency-groups].mygroup.requires-python (#13735)requires-python (#14076)platform_machine marker for win_amd64 platform tag (#14041)dependency-groups from pyproject.tomls with no [project] (#13742)uv init --script (#14141)uv run (#14153)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.14/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.14/uv-installer.ps1 | iex"
Fix stability of uuid.getnode on 3.13
uuid.getnode on 3.13See the python-build-standalone release notes for more details.
uv python pin if not found (#13946)zstd and deflate to Accept-Encoding (#13982)uv python pin (#13944)uv add --group ... --script (#13997)llms.txt to uv (#13929)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.13/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.13/uv-installer.ps1 | iex"
Add uv python pin --rm to remove .python-version pins
uv python pin --rm to remove .python-version pins (#13860)excluded-newer (#13884)tool.uv.environments on resolution error (#13455)tool.uv.required-environments on resolution error (#13575)python pin error messages (#13862)uv sync, uv add and uv remove to prevent race conditions (#13869)--no-editable to uv export for pylock.toml (#13852).gitignore in project init files (#13855)gh auth login (#13850)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.12/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.12/uv-installer.ps1 | iex"
Better error message for version specifier with missing operator
reqwest and hyper-util to resolve connection reset errors over IPv6 (#13835)uv's binary's version when checking if it's up to date (#13840)SIGINT docs (#13787)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.11/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.11/uv-installer.ps1 | iex"
Add --show-extras to uv tool list
--show-extras to uv tool list (#13783)git username when using SSH authentication (#13799)/+simple (#13743)uv export (#13809)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.10/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.10/uv-installer.ps1 | iex"
The changes reverted in 0.7.8 have been restored.
The changes reverted in 0.7.8 have been restored.
See the
python-build-standalone release notes
for more details.
uvx (#13583)uvw as alias for uv without console window on Windows (#11786)uv python list (#13721)extends-environment key in the pyvenv.cfg file of an ephemeral environment (#13598)uv-python crate's manylinux submodule (#11131)Version display (#13643)uv cache clean (#13669)--all-packages (#13678)self update if global --offline is set (#13663)uv python install --reinstall (#13645)LC_ALL=C for git when checking git worktree (#13637)uv add --bounds to configure version constraints (#12946)exclude-newer date format for persistent configuration files (#13706).pre-commit-config.yaml (#10243)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.9/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.9/uv-installer.ps1 | iex"
We are reverting most of our Python changes from uv 0.7.6 and uv 0.7.7 due to a miscompilation that makes the Python interpreter behave incorrectly, r
We are reverting most of our Python changes from uv 0.7.6 and uv 0.7.7 due to
a miscompilation that makes the Python interpreter behave incorrectly, resulting
in spurious type-errors involving str. This issue seems to be isolated to
x86_64 Linux, and affected at least Python 3.12, 3.13, and 3.14.
The following changes that were introduced in those versions of uv are temporarily being reverted while we test and deploy a proper fix for the miscompilation:
libpython into the interpreter on Linux for a significant performance boostcurl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.8/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.8/uv-installer.ps1 | iex"
Work around third-party packages that (incorrectly) assume the interpreter is dynamically linking libpython
See the python-build-standalone release notes for more details.
uv version lock and sync (#13317)ldd in diagnostics to correctly refer to ld.so (#13552)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.7/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.7/uv-installer.ps1 | iex"
Add free-threaded Python on musl
libpython into the interpreter on Linux for a significant performance boostSee the
python-build-standalone release notes
for more details.
VIRTUAL_ENV_PROMPT value (#13501)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.6/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.6/uv-installer.ps1 | iex"
Support case-sensitive module discovery in the build backend
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.5/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.5/uv-installer.ps1 | iex"
Add more context to external errors
uv add (#13462)--raw-sources to --raw (#13348)self update is used to install an older version (#13340)uv self update if required uv version is newer (#13305)pylock.toml dependency entries (#13384).tgz parsing to respect true extension (#13382)pylock.toml in uv add -r (#13421)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.4/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.4/uv-installer.ps1 | iex"
Add --dry-run support to uv self update
--dry-run support to uv self update (#9829)--show-with to uv tool list to list packages included by --with (#13264)fs_err for paths in symlinking errors (#13303)python-downloads-json-url option for uv.toml to configure custom Python installations via JSON URL (#12974)musllinux_1_0 as a valid platform tag (#13289)uv run --with (#13283)uv run --with (#13284)--no-sync (#13287)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.3/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.3/uv-installer.ps1 | iex"
Improve trace log for retryable errors
uv version is used with project-specific flags but no project is found (#13203)clang in managed Python sysconfig (#13237)--project in uv version (#13230)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.2/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.2/uv-installer.ps1 | iex"
Revert fix handling of authentication when encountering redirects
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.7.1/uv-installer.sh | sh
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.7.1/uv-installer.ps1 | iex"
One column per month.