Astral released uv 0.13.8 on 12 November 2026. It is a point release, but it touches three things most Python teams care about: trying new interpreters, protecting installs from bad uploads, and keeping credentials safe on shared machines. This guide goes through the changes from the official release notes and shows the commands. Every command here was run against uv 0.13.8.
What’s in uv 0.13.8
- CPython 3.16.0a2 is now available as a managed Python.
- Managed CPython 3.11–3.15 builds now include pip 26.3, zlib 1.4 and Expat 2.10.0. GraalPy 3.13.0 moves to build 25.5.5.
- Per-index
exclude-newer-packagecutoffs are now honoured during resolution. - Plaintext credential files on Unix are now owner-only.
- Concurrent
uvxoruv run --withcalls that need the same environment no longer build it twice. - Fixes for negative extra markers on constraints, recursive extras from scoped overrides, and
activate.batpaths that contain apostrophes. - Preview work on wheel variants (CPU- and accelerator-specific wheels).
Step 1: Upgrade
If you installed uv with the standalone installer:
uv self update
uv --version # uv 0.13.8
If you installed it with pip or pipx, upgrade it the same way. In CI, pin the version in your setup step so builds stay reproducible.
Step 2: Try Python 3.16 alpha 2 without touching your system
uv downloads and manages interpreters for you, so testing an alpha takes one command and needs no admin rights:
uv python list --all-versions | grep 3.16
uv run --python 3.16.0a2 --no-project python -c "import sys; print(sys.version)"
On our test machine the second command downloaded the build and printed 3.16.0a2 (main, Nov 11 2026, ...). A free-threaded build (3.16.0a2+freethreaded) is listed too.
To run your test suite on the alpha without changing the project’s normal interpreter:
uv run --python 3.16.0a2 --with pytest pytest -q
Alphas are for finding problems early, not for production. Run them in a separate CI job that is allowed to fail.
Step 3: Add a dependency “cooldown”
Supply-chain attacks often rely on a bad version being installed in the first hours after upload, before anyone notices. uv’s exclude-newer setting tells the resolver to ignore anything uploaded after a cutoff. The cutoff accepts an RFC 3339 timestamp, a local date, a “friendly” duration such as 7 days, or an ISO 8601 duration such as P7D.
A rolling seven-day cooldown in pyproject.toml:
[tool.uv]
exclude-newer = "7 days"
Now uv lock and uv add only consider releases that are at least a week old.
Exceptions for a single package
Sometimes one package needs a different cutoff. You may need a security fix released yesterday, or you may want to hold one library at an older snapshot. Use exclude-newer-package:
[tool.uv]
exclude-newer = "7 days"
exclude-newer-package = { httpx = "2025-01-01" }
The same works on the command line with uv pip compile:
uv pip compile requirements.in \
--exclude-newer 2026-01-01 \
--exclude-newer-package "requests=2025-06-01"
In our test this resolved requests==2.32.3, the last release before the per-package date, while the other packages followed the global cutoff.
What 0.13.8 fixed here
If you set exclude-newer-package cutoffs per index (for example a private index plus PyPI), earlier versions could ignore them during resolution. 0.13.8 honours them. If you use multiple indexes with cutoffs, upgrade and re-lock, then review the lockfile diff.
Step 4: Check your credential files
uv can store index credentials in plaintext files when no keyring is available, which is common on CI runners and servers. In 0.13.8, uv restricts these files to owner-only permissions on Unix. That matters on shared build machines, where other users could otherwise read your private index token.
What to do:
- Upgrade uv on shared machines first.
- Find uv’s credentials directory and check files written by earlier versions:
uv auth dir # prints the credentials directory, e.g. ~/.local/share/uv/credentials
ls -l "$(uv auth dir)" # look for files readable by group or others
chmod 600 "$(uv auth dir)"/*
- Prefer environment variables or your CI’s secret store for tokens where possible, and rotate any token that may have been readable by others.
Step 5: Faster parallel uvx runs
Many teams run tools such as ruff, mypy or a code generator through uvx in parallel jobs or pre-commit hooks. Before 0.13.8, two concurrent calls that needed the same throwaway environment could each build it. Now uv avoids the duplicate build. There is nothing to configure, so you simply get less wasted CPU and fewer cache races in monorepos.
# both commands now share one environment build
uvx ruff check . & uvx ruff format --check . & wait
Preview: wheel variants
Wheel variants let a package publish several builds of the same version, for example tuned for an x86-64 microarchitecture level or a specific accelerator, and let the installer choose the right one. In 0.13.8 the preview gained:
- installing variants from local paths, direct URLs and Git repositories in platform-specific resolutions
- detection of x86-64 microarchitecture levels and AArch64 architecture versions
- detection of Google TPUs
- a CPU detection fix on macOS with GraalPy
This is still a preview feature, so don’t depend on it in production. If you publish native extensions, especially ML libraries, it’s worth following because it could replace today’s messy “pick the right index URL” instructions.
Other fixes worth knowing
- Negative extra markers on constraints are respected. If you used constraints such as
foo; extra != "bar", re-lock to pick up correct behaviour. - Recursive extras from a scoped override now resolve their dependencies.
- Windows
activate.batworks when the virtual environment path contains an apostrophe, for example underC:\Users\O'Brien\. uv auditreports quarantined packages even when index URLs differ only in redacted query values.- The docs now note that GitLab CI job images need a shell.
A safe upgrade checklist
- Run
uv self update, or bump the pinned version in CI. - Run
uv lockand review the diff, especially if you use multiple indexes or constraints. - Add
exclude-newer = "7 days"if you don’t have a cooldown yet. - Fix permissions on old credential files on shared runners.
- Add an optional CI job on
3.16.0a2to catch problems early.
Takeaway
uv 0.13.8 is small but useful. It makes Python 3.16 alpha testing a one-liner, makes per-index cutoffs behave correctly, and tightens credential file permissions. Pair it with a rolling exclude-newer cooldown and you get a cheap, meaningful defence against bad releases. Full details are in the uv 0.13.8 release notes.
