Sourced from uv-build's releases.

0.11.0

Release Notes

Released on 2026-03-23.

Breaking changes

This release includes changes to the networking stack used by uv. While we think that breakage will be rare, it is possible that these changes will result in the rejection of certificates previously trusted by uv so we have marked the change as breaking out of an abundance of caution.

The changes are largely driven by the upgrade of reqwest, which powers uv's HTTP clients, to v0.13 which included some breaking changes to TLS certificate verification.

The following changes are included:

• rustls-platform-verifier is used instead of rustls-native-certs and webpki for certificate verification

  This change should have no effect unless you are using the native-tls option to enable reading system certificates.

  rustls-platform-verifier delegates to the system for certificate validation (e.g., Security.framework on macOS) instead of eagerly loading certificates from the system and verifying them via webpki. The effects of this change will vary based on the operating system. In general, uv's certificate validation should now be more consistent with browsers and other native applications. However, this is the most likely cause of breaking changes in this release. Some previously failing certificate chains may succeed, and some previously accepted certificate chains may fail. In either case, we expect the validation to be more correct and welcome reports of regressions.

  In particular, because more responsibility for validating the certificate is transferred to your system's security library, some features like CA constraints or revocation of certificates via OCSP and CRLs may now be used.

  This change should improve performance when using system certificate on macOS, as uv no longer needs to load all certificates from the keychain at startup.

• aws-lc is used instead of ring for a cryptography backend

  There should not be breaking changes from this change. We expect this to expand support for certificate signature algorithms.

• --native-tls is deprecated in favor of a new --system-certs flag

  The --native-tls flag is still usable and has identical behavior to --system-certs.

  This change was made to reduce confusion about the TLS implementation uv uses. uv always uses rustls not native-tls.

• Building uv on x86-64 and i686 Windows requires NASM

  NASM is required by aws-lc. If not found on the system, a prebuilt blob provided by aws-lc-sys will be used.

  If you are not building uv from source, this change has no effect.

  See the CONTRIBUTING guide for details.

• Empty SSL_CERT_FILE values are ignored (for consistency with SSL_CERT_DIR)

See #18550 for details.

Python

• Enable frame pointers for improved profiling on Linux x86-64 and aarch64

See the python-build-standalone release notes for details.

... (truncated)

Sourced from uv-build's changelog.

0.11.0

Released on 2026-03-23.

Breaking changes

This release includes changes to the networking stack used by uv. While we think that breakage will be rare, it is possible that these changes will result in the rejection of certificates previously trusted by uv so we have marked the change as breaking out of an abundance of caution.

The changes are largely driven by the upgrade of reqwest, which powers uv's HTTP clients, to v0.13 which included some breaking changes to TLS certificate verification.

The following changes are included:

• rustls-platform-verifier is used instead of rustls-native-certs and webpki for certificate verification

  This change should have no effect unless you are using the native-tls option to enable reading system certificates.

  rustls-platform-verifier delegates to the system for certificate validation (e.g., Security.framework on macOS) instead of eagerly loading certificates from the system and verifying them via webpki. The effects of this change will vary based on the operating system. In general, uv's certificate validation should now be more consistent with browsers and other native applications. However, this is the most likely cause of breaking changes in this release. Some previously failing certificate chains may succeed, and some previously accepted certificate chains may fail. In either case, we expect the validation to be more correct and welcome reports of regressions.

  In particular, because more responsibility for validating the certificate is transferred to your system's security library, some features like CA constraints or revocation of certificates via OCSP and CRLs may now be used.

  This change should improve performance when using system certificate on macOS, as uv no longer needs to load all certificates from the keychain at startup.

• aws-lc is used instead of ring for a cryptography backend

  There should not be breaking changes from this change. We expect this to expand support for certificate signature algorithms.

• --native-tls is deprecated in favor of a new --system-certs flag

  The --native-tls flag is still usable and has identical behavior to --system-certs.

  This change was made to reduce confusion about the TLS implementation uv uses. uv always uses rustls not native-tls.

• Building uv on x86-64 and i686 Windows requires NASM

  NASM is required by aws-lc. If not found on the system, a prebuilt blob provided by aws-lc-sys will be used.

  If you are not building uv from source, this change has no effect.

  See the CONTRIBUTING guide for details.

• Empty SSL_CERT_FILE values are ignored (for consistency with SSL_CERT_DIR)

See #18550 for details.

Python

• Enable frame pointers for improved profiling on Linux x86-64 and aarch64

See the python-build-standalone release notes for details.

... (truncated)

• 1f31f0e Bump version to 0.11.0 (#18683)
• e280625 Resolve official uv self-update versions before axoupdater (#18674)
• 10477cd Split the alternative indexes page into separate pages (#18607)
• 8a712b0 Treat paths originating as PEP 508 URLs which contain expanded variables as r...
• b0ad910 Fix export of conflicting workspace members with dependencies (#18666)
• 3f215e4 Disable deployment on environment use (#18677)
• 47edbf9 Clarify FLASH_ATTENTION_SKIP_CUDA_BUILD guidance for flash-attn installs...
• 6a7c882 Update Rust crate reqsign to 0.20.0 (#17935)
• b6854d7 Upgrade reqwest to 0.13 (#18550)
• c43c0d0 Add tests for uv_pep508::verbatim_url::expand_env_vars (#18676)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)