Update dependency uv to v0.9.3 (16/edge) #1222
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
added
the
not bug or enhancement
renovate
bot
requested review from
a team,
dragomirp,
marceloneppel and
taurus-forever
and removed request for
a team
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project status has failed because the head coverage (66.94%) is below the target coverage (70.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## 16/edge #1222 +/- ##
========================================
Coverage 66.94% 66.94%
========================================
Files 17 17
Lines 4347 4347
Branches 671 671
========================================
Hits 2910 2910
Misses 1242 1242
Partials 195 195 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
taurus-forever
approved these changes
Oct 15, 2025
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/16/edge-charmcraft.yaml-build-tools
branch
from
e97b3e0 to
023c490
Compare
dragomirp
approved these changes
Oct 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.8.23->0.9.3Release Notes
astral-sh/uv (uv)
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
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.8.24/uv-installer.ps1 | iex"Download uv 0.8.24
Configuration
📅 Schedule: Branch creation - Between 01:00 AM and 05:59 AM, only on Tuesday ( * 1-5 * * 2 ) in timezone Etc/UTC, 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 was generated by Mend Renovate. View the repository job log.