chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.11.2

[renovate-bot-cbcoutinho]

This PR contains the following updates:

Package	Type	Update	Change
ghcr.io/astral-sh/uv	final	minor	0.10.12 → 0.11.2

---

Release Notes

astral-sh/uv (ghcr.io/astral-sh/uv)

v0.11.2

Compare Source

Released on 2026-03-26.

Enhancements

• Add a dedicated Windows PE editing error (#​18710)
• Make uv self update fetch the manifest from the mirror first (#​18679)
• Use uv reqwest client for self update (#​17982)
• Show uv self update success and failure messages with --quiet (#​18645)

Preview features

• Evaluate extras and groups when determining auditable packages (#​18511)

Bug fixes

• Skip redundant project configuration parsing for uv run (#​17890)

v0.11.1

Compare Source

Released on 2026-03-24.

Bug fixes

• Add missing hash verification for riscv64gc-unknown-linux-musl (#​18686)
• Fallback to direct download when direct URL streaming is unsupported (#​18688)
• Revert treating 'Dynamic' values as case-insensitive (#​18692)
• Remove torchdata from list of packages to source from the PyTorch index (#​18703)
• Special-case == Python version request ranges (#​9697)

Documentation

• Cover --python <dir> in "Using arbitrary Python environments" (#​6457)
• Fix version annotations for PS_MODULE_PATH and UV_WORKING_DIR (#​18691)

v0.11.0

Compare 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-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.

Enhancements

• Treat 'Dynamic' values as case-insensitive (#​18669)
• Use a dedicated error for invalid cache control headers (#​18657)
• Enable checksum verification in the generated installer script (#​18625)

Preview features

• Add --service-format and --service-url to uv audit (#​18571)

Performance

• Avoid holding flat index lock across indexes (#​18659)

Bug fixes

• Find the dynamic linker on the file system when sniffing binaries fails (#​18457)
• Fix export of conflicting workspace members with dependencies (#​18666)
• Respect installed settings in uv tool list --outdated (#​18586)
• Treat paths originating as PEP 508 URLs which contain expanded variables as relative (#​18680)
• Fix uv export for workspace member packages with conflicts (#​18635)
• Continue to alternative authentication providers when the pyx store has no token (#​18425)
• Use redacted URLs for log messages in cached client (#​18599)

Documentation

• Add details on Linux versions to the platform policy (#​18574)
• Clarify FLASH_ATTENTION_SKIP_CUDA_BUILD guidance for flash-attn installs (#​18473)
• Split the dependency bots page into two separate pages (#​18597)
• Split the alternative indexes page into separate pages (#​18607)

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[claude]

PR Review: chore(deps): update uv Docker tag to v0.11.0

This is a routine Renovate Bot dependency update (single-line Dockerfile change).

Assessment: Looks good to merge.

Positive notes:

• SHA digest is pinned, which is a security best practice
• New digest matches the published v0.11.0 release

Notable in v0.11.0 (potential breaking changes to be aware of):

• rustls-platform-verifier replaces rustls-native-certs + webpki for TLS certificate verification. Some previously-accepted certificate chains may fail or vice versa.
• aws-lc replaces ring as the cryptography backend (no breaking changes expected)
• --native-tls is deprecated in favor of --system-certs (still functional)

Impact on this project: The Dockerfile uses python:3.12-slim-trixie (minimal Debian). No --native-tls flag is used in the Dockerfile, so TLS changes should be a non-issue for the Docker build process.

No concerns with code quality, security, test coverage, or performance.

[claude]

PR Review: Dependency update — uv 0.10.12 → 0.11.2

This is a clean Renovate-generated update. A few notes:

✅ Looks good:

• SHA digest is pinned (good security practice — prevents tag mutation attacks)
• Only a single line changed in the Dockerfile
• The tag and digest are consistent with each other

⚠️ Notable change to be aware of:
uv v0.11.0 is a minor version bump with a breaking change in its networking/TLS stack:

• Switched from rustls-native-certs + webpki to rustls-platform-verifier for certificate validation
• This is most relevant if the build environment or runtime uses custom/self-signed certificates (e.g., a private Nextcloud instance behind a corporate CA)
• In a standard Docker build environment this should be a non-issue, but worth being aware of if CI or integration tests interact with any TLS endpoints during the build

No concerns for code quality, security (digest pinning is correct), or test coverage — this is purely a toolchain bump. Safe to merge assuming CI passes.