Summary
I am running on a 2021 M1 macbook pro with Sequoia 15.7.4.
For background, I recently was testing a uv-based build to use in an air-gapped context, and to do a quick-and-dirty test on my mac, I installed a fresh version of uv. I did so using the script-based workflow and the UV_INSTALL_DIR=<dir> flag/var. It was at this point that uv appeared to be fully broken. Every command seemed to generate errors of the flavor:
thread 'main2' (1920128) panicked at crates/uv-client/src/base_client.rs:581:14:
Failed to build HTTP client.: reqwest::Error { kind: Builder, source: InvalidCertificate(Other(OtherError(UnsupportedCriticalExtension))) }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' (1920127) panicked at crates/uv/src/lib.rs:2788:10:
Tokio executor failed, was there a panic?: Any { .. }I ended up spending the better part of a day debugging, doing such things as:
- Furiously combing the uv docs
- Explicitly providing
--system-certs and setting SSL_CERT_{DIR,FILE} (I'm behind a company network on vpn, unproxied)
- Trying the other VPN that is proxied, with systems env variables set.
- Disconnecting from company network.
- Switching to the PyPi index from our internal index, while on the company network.
- Reinstalling rust, rustup, python...
In the end, I finally landed on downgrading to uv v0.10.12, and voila! everything is back to working as expected.
Just to be sure, I reinstalled the latest, v0.11.3, and the errors were back, exactly the same. Downgraded to v0.10, and working again. I also tested all the v0.11.x versions and can confirm they do not work for me.
All this said... I am reasonably confident this is not a peculiarity to my specific setup, but that's a tricky one to rule out. Much more likely that I'm doing something silly 🙃
Let me know if I can provide further info, and I'll include a minimal-reproducer below
$ uname -a
Darwin <hostname> 24.6.0 Darwin Kernel Version 24.6.0: [...]
$ sw_vers
ProductName: macOS
ProductVersion: 15.7.4
BuildVersion: 24G517
$ uv --version
uv 0.10.12 (00d72dac7 2026-03-19 aarch64-apple-darwin)
$ uv cache clean
Clearing cache at: <HOME>/.cache/uv
Removed 269 files (7.3MiB)
$ mkdir uv-test-0.10 && cd uv-test-0.10
$ uv init
Initialized project `uv-test-0-10`
$ uv add requests
Using CPython 3.14.3 interpreter at: <PATH>/bin/python3.14
Creating virtual environment at: .venv
Resolved 6 packages in 567ms
Prepared 5 packages in 204ms
Installed 5 packages in 16ms
+ certifi==2026.2.25
+ charset-normalizer==3.4.7
+ idna==3.11
+ requests==2.33.1
+ urllib3==2.6.3
$ cd ..
$ curl -LsSf https://astral.sh/uv/install.sh | sh
downloading uv 0.11.3 aarch64-apple-darwin
installing to <HOME>/.local/bin
uv
uvx
everything's installed!
$ uv cache clean
Clearing cache at: <HOME>/.cache/uv
Removed 137 files (3.6MiB)
$ mkdir uv-test-0.11 && cd uv-test-0.11
$ uv init
thread 'main2' (1958661) panicked at crates/uv-client/src/base_client.rs:581:14:
Failed to build HTTP client.: reqwest::Error { kind: Builder, source: InvalidCertificate(Other(OtherError(UnsupportedCriticalExtension))) }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' (1958660) panicked at crates/uv/src/lib.rs:2788:10:
Tokio executor failed, was there a panic?: Any { .. }
$ curl -LsSf https://astral.sh/uv/0.10.12/install.sh | sh
downloading uv 0.10.12 aarch64-apple-darwin
no checksums to verify
installing to <HOME>/.local/bin
uv
uvx
everything's installed!
$ uv init
Initialized project `uv-test-0-11`
$ uv add requests
Using CPython 3.14.3 interpreter at: <PATH>/bin/python3.14
Creating virtual environment at: .venv
Resolved 6 packages in 443ms
Prepared 5 packages in 168ms
Installed 5 packages in 25ms
+ certifi==2026.2.25
+ charset-normalizer==3.4.7
+ idna==3.11
+ requests==2.33.1
+ urllib3==2.6.3Platform
MacOS 15.7.4, arm64 (M1 Max)
Version
uv 0.11.x
Python version
Python 3.14.3
Summary
I am running on a 2021 M1 macbook pro with Sequoia 15.7.4.
For background, I recently was testing a uv-based build to use in an air-gapped context, and to do a quick-and-dirty test on my mac, I installed a fresh version of uv. I did so using the script-based workflow and the
UV_INSTALL_DIR=<dir>flag/var. It was at this point that uv appeared to be fully broken. Every command seemed to generate errors of the flavor:I ended up spending the better part of a day debugging, doing such things as:
--system-certsand settingSSL_CERT_{DIR,FILE}(I'm behind a company network on vpn, unproxied)In the end, I finally landed on downgrading to uv v0.10.12, and voila! everything is back to working as expected.
Just to be sure, I reinstalled the latest, v0.11.3, and the errors were back, exactly the same. Downgraded to v0.10, and working again. I also tested all the v0.11.x versions and can confirm they do not work for me.
All this said... I am reasonably confident this is not a peculiarity to my specific setup, but that's a tricky one to rule out. Much more likely that I'm doing something silly 🙃
Let me know if I can provide further info, and I'll include a minimal-reproducer below
Platform
MacOS 15.7.4, arm64 (M1 Max)
Version
uv 0.11.x
Python version
Python 3.14.3