uvReleasedpatch

uv 0.13.2 is out: highlights and upgrade guide

At a glance

uv 0.13.2 is a patch release published on Oct 19, 2026. It follows uv 0.13.1 by 5 days. It includes 31 listed changes.

  • Report all installed packages in uv workspace metadata, including packages outside the selected resolution
  • Include supported environment restrictions when exporting pylock.toml
  • Retry dropped GET and HEAD requests when fetching package and index data
  • Preserve encoding declarations in wheel data scripts that require shell launchers
  • Show causes and hints when uv python find --script cannot discover an interpreter, including with -q
Version
0.13.2
Released
Oct 19, 2026
Release type
Patch
Previous
0.13.1
Changes listed
31
License
Apache-2.0

How to upgrade to uv 0.13.2

This is a patch release, normally bug fixes only. It is usually safe to upgrade after your tests pass.

uv
uv self update 0.13.2

What's included in uv 0.13.2

Details from the official release page.

Enhancements

  • Report all installed packages in uv workspace metadata, including packages outside the selected resolution (#22395)
  • Include supported environment restrictions when exporting pylock.toml (#22596)
  • Retry dropped GET and HEAD requests when fetching package and index data (#22672)
  • Preserve encoding declarations in wheel data scripts that require shell launchers (#22526)
  • Show causes and hints when uv python find --script cannot discover an interpreter, including with -q (#22549)
  • Print valid ksh activation instructions and support non-relocatable environments under OpenBSD-derived ksh (#22538, #22572)
  • Allow PEP 508 direct URLs, including Mercurial and extensionless archive URLs, in uv-build's [build-system].requires validation (#22577)

Python

  • Add PyPy 3.11.17 and 3.12.15 (#22578)

Preview features

  • Fetch and parse PEP 825 index-level variant metadata with wheel-variants (#22509, #22511)

Performance

  • Avoid exponential work when simplifying, traversing, and exporting complex dependency markers (#22608, #22615, #22651, #22674)
  • Reduce the time and memory used to parse and store complex dependency markers (#22675, #22676, #22681)
  • Reduce resolver memory use for large dependency graphs, forks, extras, and dependency groups (#22565, #22625)
  • Speed up project discovery in large workspaces by caching member names (#22635)
  • Reduce uv's binary size and speed up CycloneDX exports (#22431)
  • Reduce uv-build binary size, including Linux x86_64 wheels (#22539, #22573)
  • Reduce allocations when parsing TOML (#22679)

Bug fixes

  • Respect --exclude-newer when a newer wheel for the selected source distribution is already cached (#22685)
  • Prevent URL credentials from leaking through diagnostics or persisted metadata (#22600, #22601, #22617, #22622, #22646)
  • Keep separate cache entries for signed --find-links URLs that differ only in sensitive query values (#22630)
  • Honor PEP 751 environment restrictions when installing or syncing from pylock.toml (#22594)
  • Use configured credentials before prompting during uv publish, and avoid prompting when no upload occurs (#22593)
  • Match recursive build globs against complete file paths and ignore invalid license symlinks (#22581, #22583)
  • Return an error for invalid uv pip compile --python-version values instead of panicking (#22727)
  • Reject invalid pylock.toml output filenames before resolution instead of panicking (#22725)
  • Avoid panicking during repeated resolution conflicts involving fixed-priority packages (#22589)
  • Create version aliases correctly when installing managed Python into a relative directory (#22547)
  • Show incompatibilities from failing uv pip check invocations with -q (#22544)
  • Treat logically equivalent dependency markers as equal regardless of construction order (#22680)

Rust API

  • Require the opt-in unsafe-url feature to use raw url::Url APIs in uv-pep508 (#22623)

Documentation

  • Clarify credential lookup, environment synchronization, managed Python, and integration guidance (#22542)

Other changes

  • Use stable sh.astral.* signing identifiers for macOS binaries (#22648)

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:

uv 0.13.2 FAQ

When was uv 0.13.2 released?

uv 0.13.2 was published on Oct 19, 2026.

Is uv 0.13.2 a major update?

No. It is a patch release, mainly bug fixes.

How do I upgrade to uv 0.13.2?

Use the commands in the “How to upgrade” section, then run your test suite.

Where are the official uv 0.13.2 notes?

On the project's official release page: https://github.com/astral-sh/uv/releases/tag/0.13.2

Source: official uv 0.13.2 release. Spotted an error? Tell us.