Merged
Merged
Conversation
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| astral-sh/uv | uses-with | minor | 0.8.23 -> 0.9.2 |
Release Notes
astral-sh/uv (astral-sh/uv)v0.9.2
Released on 2025-10-10.
Python
- Add CPython 3.9.24.
- Add CPython 3.10.19.
- Add CPython 3.11.14.
- Add CPython 3.12.12.
Enhancements
Documentation
- Add missing "added in" to new environment variables in reference (#16217)
v0.9.1
Released on 2025-10-09.
Enhancements
Configuration
- Add
UV_UPLOAD_HTTP_TIMEOUTand respectUV_HTTP_TIMEOUTin uploads (#16040) - Support
UV_WORKING_DIRECTORYfor setting--directory(#16125)
Bug fixes
- Allow missing
Scriptsdirectory (#16206) - Fix handling of Python requests with pre-releases in ranges (#16208)
- Preserve comments on version bump (#16141)
- Retry all HTTP/2 errors (#16038)
- Treat deleted Windows registry keys as equivalent to missing ones (#16194)
- Ignore pre-release Python versions when a patch version is requested (#16210)
Documentation
- Document why uv discards upper bounds on
requires-python(#15927) - Document uv version environment variables were added in (#15196)
v0.9.0
Released on 2025-10-07.
Breaking changes
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.
There are no breaking changes to uv_build. If you have an upper bound in your [build-system] table, you should update it.
-
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-alpineor
python:3.14-rc-trixie. Now, the-rcsuffix has been removed to match the stable
upstream images. The-rcimages tags will no longer be
updated. 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
- Add CPython 3.14.0
- Add CPython 3.13.8
Enhancements
- Don't warn when dependency is constraint by other dependency (#16149)
Bug fixes
- Fix
uv python upgrade / installoutput when there is a no-op for one request (#16158) - Surface pinned-version hint when
uv tool upgradecan’t move the tool (#16081) - Ban pre-release versions in
uv python upgraderequests (#16160) - Fix
uv python upgradereplacement of installed binaries on pre-release to stable (#16159)
Documentation
- Update
uv pip compileargs inlayout.md(#16155)
v0.8.24
Released on 2025-10-06.
Enhancements
- Emit a message on
cache cleanandprunewhen lock is held (#16138) - Add
--forceflag foruv cache prune(#16137)
Documentation
- Fix example of bumping beta version without patch bump (#16132)
Configuration
📅 Schedule: Branch creation - Only on Sunday and Saturday ( * * * * 0,6 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.