Update ghcr.io/astral-sh/uv Docker tag to v0.9.5 #107
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: imcompiling/dakiny-bot#107
Reference in New Issue
Block a user
This PR contains the following updates:
0.8.23->0.9.5Release Notes
astral-sh/uv (ghcr.io/astral-sh/uv)
v0.9.5Compare Source
Released on 2025-10-21.
This release contains an upgrade to
astral-tokio-tar, which addresses a vulnerability in tar extraction on malformed archives with mismatching size information between the ustar header and PAX extensions. While theastral-tokio-taradvisory has been graded as "high" due its potential broader impact, the specific impact to uv is low due to a lack of novel attacker capability. Specifically, uv only processes tar archives from source distributions, which already possess the capability for full arbitrary code execution by design, meaning that an attacker gains no additional capabilities throughastral-tokio-tar.Regardless, we take the hypothetical risk of parser differentials very seriously. Out of an abundance of caution, we have assigned this upgrade an advisory: https://github.com/astral-sh/uv/security/advisories/GHSA-w476-p2h3-79g9
Security
astral-tokio-tarto 0.5.6 to address a parsing differential (#16387)Enhancements
uv pip installfailure if the--systemflag is used to select an externally managed interpreter (#16318)Bug fixes
Documentation
v0.9.4Compare Source
Released on 2025-10-17.
Enhancements
Bug fixes
uv auth tokenoutput (#16345)v0.9.3Compare Source
Released on 2025-10-14.
Python
Enhancements
Bug fixes
v0.9.2Compare Source
Released on 2025-10-10.
Python
Enhancements
uv publish(#16234)uv tool list --show-python(#15814)Documentation
v0.9.1Compare Source
Released on 2025-10-09.
Enhancements
uv init(#16182)pylock.tomlconfig conflict error messages (#16211)Configuration
UV_UPLOAD_HTTP_TIMEOUTand respectUV_HTTP_TIMEOUTin uploads (#16040)UV_WORKING_DIRECTORYfor setting--directory(#16125)Bug fixes
Scriptsdirectory (#16206)Documentation
requires-python(#15927)v0.9.0Compare Source
Released on 2025-10-07.
This breaking release is primarily motivated by the release of Python 3.14, which contains some breaking changes (we recommend reading the "What's new in Python 3.14" page). uv may use Python 3.14 in cases where it previously used 3.13, e.g., if you have not pinned your Python version and do not have any Python versions installed on your machine. While we think this is uncommon, we prefer to be cautious. We've included some additional small changes that could break workflows.
See our Python 3.14 blog post for some discussion of features we're excited about!
There are no breaking changes to
uv_build. If you have an upper bound in your[build-system]table, you should update it.Breaking changes
Python 3.14 is now the default stable version
The default Python version has changed from 3.13 to 3.14. This applies to Python version installation when no Python version is requested, e.g.,
uv python install. By default, uv will use the system Python version if present, so this may not cause changes to general use of uv. For example, if Python 3.13 is installed already, thenuv venvwill use that version. If no Python versions are installed on a machine and automatic downloads are enabled, uv will now use 3.14 instead of 3.13, e.g., foruv venvoruvx python. This change will not affect users who are using a.python-versionfile to pin to a specific Python version.Allow use of free-threaded variants in Python 3.14+ without explicit opt-in (#16142)
Previously, free-threaded variants of Python were considered experimental and required explicit opt-in (i.e., with
3.14t) for usage. Now uv will allow use of free-threaded Python 3.14+ interpreters without explicit selection. The GIL-enabled build of Python will still be preferred, e.g., when performing an installation withuv python install 3.14. However, e.g., if a free-threaded interpreter comes before a GIL-enabled build on thePATH, it will be used. This change does not apply to free-threaded Python 3.13 interpreters, which will continue to require opt-in.Use Python 3.14 stable Docker images (#16150)
Previously, the Python 3.14 images had an
-rcsuffix, e.g.,python:3.14-rc-alpineorpython:3.14-rc-trixie. Now, the-rcsuffix has been removed to match the stableupstream images. The
-rcimages tags will no longer beupdated. This change should not break existing workflows.
Upgrade Alpine Docker image to Alpine 3.22
Previously, the
uv:alpineDocker image was based on Alpine 3.21. Now, this image is based on Alpine 3.22. The previous image can be recovered withuv:alpine3.21and will continue to be updated until a future release.Upgrade Debian Docker images to Debian 13 "Trixie"
Previously, the
uv:debiananduv:debian-slimDocker images were based on Debian 12 "Bookworm". Now, these images are based on Debian 13 "Trixie". The previous images can be recovered withuv:bookwormanduv:bookworm-slimand will continue to be updated until a future release.Fix incorrect output path when a trailing
/is used inuv build(#15133)When using
uv buildin a workspace, the artifacts are intended to be written to adistdirectory in the workspace root. A bug caused workspace root determination to fail when the input path included a trailing/causing thedistdirectory to be placed in the child directory. This bug has been fixed in this release. For example,uv build child/is used, the output path will now be in<workspace root>/dist/rather than<workspace root>/child/dist/.Python
Enhancements
Bug fixes
uv python upgrade / installoutput when there is a no-op for one request (#16158)uv tool upgradecan’t move the tool (#16081)uv python upgraderequests (#16160)uv python upgradereplacement of installed binaries on pre-release to stable (#16159)Documentation
uv pip compileargs inlayout.md(#16155)v0.8.24Compare Source
Release Notes
Released on 2025-10-06.
Enhancements
cache cleanandprunewhen lock is held (#16138)--forceflag foruv cache prune(#16137)Documentation
Install uv 0.8.24
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.8.24
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 ghcr.io/astral-sh/uv Docker tag to v0.9.2to Update ghcr.io/astral-sh/uv Docker tag to v0.9.4Update ghcr.io/astral-sh/uv Docker tag to v0.9.4to Update ghcr.io/astral-sh/uv Docker tag to v0.9.5