Update dependency uv_build to >=0.11.7,<0.12.0 #53
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/uv_build-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
>=0.10.6,<0.11.0→>=0.11.7,<0.12.0Release Notes
astral-sh/uv (uv_build)
v0.11.7Compare Source
Released on 2026-04-15.
Python
2026041including an OpenSSL security upgrade (#19004)Enhancements
required-versionmismatches (#18977)--exclude-newerhints (#18952)Preview features
--scripthandling inuv audit(#18970)uv audit(#18970)Bug fixes
workspace metadatain linehaul data (#18966)uv sync --checkfailures (#18976)~=operators (#18960)v0.11.6Compare Source
Released on 2026-04-09.
This release resolves a low severity security advisory in which wheels with malformed RECORD entries could delete arbitrary files on uninstall. See GHSA-pjjw-68hj-v9mw for details.
Bug fixes
RECORDduring installation (#18943)uv cache cleanerrors due to Win32 path normalization (#18856)v0.11.5Compare Source
Released on 2026-04-08.
Python
Enhancements
build_system.requireserror message (#18911)Preview features
exclude-newerto[[tool.uv.index]](#18839)uv audit: add context/warnings for ignored vulnerabilities (#18905)Bug fixes
Documentation
PIP_COMPATIBILITY.mdredirect file (#18928)uv init example-bare --bareexamples (#18822, #18925)v0.11.4Compare Source
Released on 2026-04-07.
Enhancements
--upgrade-group(#18266)Bug fixes
pyproject.tomldependencies (#18786)--lockedand--frozenwhen script lockfile is missing (#18832)uv exportextra resolution for workspace member and conflicting extras (#18888)exclude-newervalues duringuv tree --outdated(#18899)--exclude-newerinuv tool list --outdated(#18861)Cargo.lockinuv-buildsource distributions (#18831)Documentation
--exclude-newercompares artifact upload times (#18830)v0.11.3Compare Source
Released on 2026-04-01.
Enhancements
uv workspace metadatawith dependency information from the lock (#18356)/installers/uv/lateston the mirror (#18725)Preview features
--ignoreand--ignore-until-fixedtouv audit(#18737)Bug fixes
blake2bhashes (#18794)powerpc64-unknown-linux-gnufrom release build targets (#18800)uv pip check(#18742)Documentation
falseopt-out forexclude-newer-package(#18768, #18803)v0.11.2Compare Source
Released on 2026-03-26.
Enhancements
uv self updatefetch the manifest from the mirror first (#18679)uv self updatesuccess and failure messages with--quiet(#18645)Preview features
Bug fixes
uv run(#17890)v0.11.1Compare Source
Released on 2026-03-24.
Bug fixes
riscv64gc-unknown-linux-musl(#18686)==Python version request ranges (#9697)Documentation
--python <dir>in "Using arbitrary Python environments" (#6457)PS_MODULE_PATHandUV_WORKING_DIR(#18691)v0.11.0Compare Source
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-verifieris used instead ofrustls-native-certsandwebpkifor certificate verificationThis change should have no effect unless you are using the
native-tlsoption to enable reading system certificates.rustls-platform-verifierdelegates to the system for certificate validation (e.g.,Security.frameworkon macOS) instead of eagerly loading certificates from the system and verifying them viawebpki. 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-lcis used instead ofringfor a cryptography backendThere should not be breaking changes from this change. We expect this to expand support for certificate signature algorithms.
--native-tlsis deprecated in favor of a new--system-certsflagThe
--native-tlsflag 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
rustlsnotnative-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 byaws-lc-syswill be used.If you are not building uv from source, this change has no effect.
See the CONTRIBUTING guide for details.
Empty
SSL_CERT_FILEvalues are ignored (for consistency withSSL_CERT_DIR)See #18550 for details.
Python
See the python-build-standalone release notes for details.
Enhancements
Preview features
--service-formatand--service-urltouv audit(#18571)Performance
Bug fixes
uv tool list --outdated(#18586)uv exportfor workspace member packages with conflicts (#18635)Documentation
FLASH_ATTENTION_SKIP_CUDA_BUILDguidance forflash-attninstalls (#18473)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
Update dependency uv_build to >=0.11.0,<0.12.0to Update dependency uv_build to >=0.11.1,<0.12.0053d347e78to7e89a8ff5fUpdate dependency uv_build to >=0.11.1,<0.12.0to Update dependency uv_build to >=0.11.2,<0.12.07e89a8ff5fto7dbfcabd8aUpdate dependency uv_build to >=0.11.2,<0.12.0to Update dependency uv_build to >=0.11.3,<0.12.07dbfcabd8ato339d00b173Update dependency uv_build to >=0.11.3,<0.12.0to Update dependency uv_build to >=0.11.4,<0.12.0339d00b173to24a924ed97Update dependency uv_build to >=0.11.4,<0.12.0to Update dependency uv_build to >=0.11.5,<0.12.024a924ed97to6a0e05e541Update dependency uv_build to >=0.11.5,<0.12.0to Update dependency uv_build to >=0.11.6,<0.12.06a0e05e541to30dee0cf9dUpdate dependency uv_build to >=0.11.6,<0.12.0to Update dependency uv_build to >=0.11.7,<0.12.030dee0cf9dtof71f37d133View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.