fix(container): update image ghcr.io/astral-sh/uv ( 0.8.5 → 0.8.8 ) - #82

v0.8.8

Compare Source

Bug fixes

• Fix find_uv_bin compatibility with Python <3.10 (#​15177)

v0.8.7

Compare Source

Python

• On Mac/Linux, libtcl, libtk, and _tkinter are built as separate shared objects, which fixes matplotlib's tkagg backend (the default on Linux), Pillow's PIL.ImageTk library, and other extension modules that need to use libtcl/libtk directly.
• Tix is no longer provided on Linux. This is a deprecated Tk extension that appears to have been previously broken.

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

Enhancements

• Do not update uv.lock when using --isolated (#​15154)
• Add support for --prefix and --with installations in find_uv_bin (#​14184)
• Add support for discovering base prefix installations in find_uv_bin (#​14181)
• Improve error messages in find_uv_bin (#​14182)
• Warn when two packages write to the same module (#​13437)

Preview features

• Add support for package-level conflicts in workspaces (#​14906)

Configuration

• Add UV_DEV and UV_NO_DEV environment variables (for --dev and --no-dev) (#​15010)

Bug fixes

• Fix regression where --require-hashes applied to build dependencies in uv pip install (#​15153)
• Ignore GraalPy devtags (#​15013)
• Include all site packages directories in ephemeral environment overlays (#​15121)
• Search in the user scheme scripts directory last in find_uv_bin (#​14191)

Documentation

• Add missing periods (.) to list elements in Features docs page (#​15138)

v0.8.6

Compare Source

This release contains hardening measures to address differentials in behavior between uv and Python's built-in ZIP parser (CVE-2025-54368).

Prior to this release, attackers could construct ZIP files that would be extracted differently by pip, uv, and other tools. As a result, ZIPs could be constructed that would be considered harmless by (e.g.) scanners, but contain a malicious payload when extracted by uv. As of v0.8.6, uv now applies additional checks to reject such ZIPs.

Thanks to a triage effort with the Python Security Response Team and PyPI maintainers, we were able to determine that these differentials were not exploited via PyPI during the time they were present. The PyPI team has also implemented similar checks and now guards against these parsing differentials on upload.

Although the practical risk of exploitation is low, we take the hypothetical risk of parser differentials very seriously. Out of an abundance of caution, we have assigned this advisory a CVE identifier and have given it a "moderate" severity suggestion.

These changes have been validated against the top 15,000 PyPI packages; however, it's plausible that a non-malicious ZIP could be falsely rejected with this additional hardening. As an escape hatch, users who do encounter breaking changes can enable UV_INSECURE_NO_ZIP_VALIDATION to restore the previous behavior. If you encounter such a rejection, please file an issue in uv and to the upstream package.

For additional information, please refer to the following blog posts:

• Astral: uv security advisory: ZIP payload obfuscation
• PyPI: Preventing ZIP parser confusion attacks on Python package installers

Security

• Harden ZIP streaming to reject repeated entries and other malformed ZIP files (#​15136)

Python

• Add CPython 3.13.6

Configuration

• Add support for per-project build-time environment variables (#​15095)

Bug fixes

• Avoid invalid simplification with conflict markers (#​15041)
• Respect UV_HTTP_RETRIES in uv publish (#​15106)
• Support UV_NO_EDITABLE where --no-editable is supported (#​15107)
• Upgrade cargo-dist to add UV_INSTALLER_URL to PowerShell installer (#​15114)
• Upgrade h2 again to avoid too_many_internal_resets errors (#​15111)
• Consider pythonw when copying entry points in uv run (#​15134)

Documentation

• Ensure symlink warning is shown (#​15126)