chore(deps): update dependency aqua:astral-sh/uv to v0.8.2 #270
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joao.dubas/ide#270
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/aqua-astral-sh-uv-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.7.20->0.8.2Release Notes
astral-sh/uv (aqua:astral-sh/uv)
v0.8.2Compare Source
Enhancements
Configuration
UV_INIT_BUILD_BACKEND(#14821)Bug fixes
Rust API
tls_built_in_root_certsfor client (#14816)Documentation
v0.8.1Compare Source
Enhancements
HF_TOKEN(#14797)--config-settings-packageto apply configuration settings at the package level (#14573)python3.13texecutables inuv venv(#14764)python -m uvin interrupted with Ctrl-C on Windows (#14715)--boundsformatting foruv_buildbounds inuv init(#14731)extrasanddependency_groupsmarkers in PEP 508 grammar (#14753)extrasanddependency_groupsmarkers onuv pip installanduv pip sync(#14755)uv self versionwhenuv versioncannot find a project (#14738)[tool.uv]fields more precise (#14325)Preview features
uv syncwith--quiet(#14810)Bug fixes
Cache-Controloverrides to response, not request headers (#14736)requires-pythoninpylock.toml(#14787)READMEvariants in build backend (#14762)pyvenv.cfglast (#14808)dependency-metadata(#14801)Documentation
setup-uvaftersetup-pythonin Github Actions integration guide (#14741)requires-pythonbehavior are consistent with pip (#14752)v0.8.0Compare Source
Since we released uv 0.7.0 in April, we've accumulated various changes that improve correctness and user experience, but could break some workflows. This release contains those changes; many have been marked as breaking out of an abundance of caution. We expect most users to be able to upgrade without making changes.
This release also includes the stabilization of a couple
uv python installfeatures, which have been available under preview since late last year.Breaking changes
Install Python executables into a directory on the
PATH(#14626)uv python installnow installs a versioned Python executable (e.g.,python3.13) into a directory on thePATH(e.g.,~/.local/bin) by default. This behavior has been available under the--previewflag since Oct 2024. This change should not be breaking unless it shadows a Python executable elsewhere on thePATH.To install unversioned executables, i.e.,
python3andpython, use the--defaultflag. The--defaultflag has also been in preview, but is not stabilized in this release.Note that these executables point to the base Python installation and only include the standard library. That means they will not include dependencies from your current project (use
uv run pythoninstead) and you cannot install packages into their environment (useuvx --with <package> pythoninstead).As with tool installation, the target directory respects common variables like
XDG_BIN_HOMEand can be overridden with aUV_PYTHON_BIN_DIRvariable.You can opt out of this behavior with
uv python install --no-binorUV_PYTHON_INSTALL_BIN=0.See the documentation on installing Python executables for more details.
Register Python versions with the Windows Registry (#14625)
uv python installnow registers the installed Python version with the Windows Registry as specified by PEP 514. This allows using uv installed Python versions via thepylauncher. This behavior has been available under the--previewflag since Jan 2025. This change should not be breaking, as using the uv Python versions withpyrequires explicit opt in.You can opt out of this behavior with
uv python install --no-registryorUV_PYTHON_INSTALL_REGISTRY=0.Prompt before removing an existing directory in
uv venv(#14309)Previously,
uv venvwould remove an existing virtual environment without confirmation. While this is consistent with the behavior of project commands (e.g.,uv sync), it's surprising to users that are using imperative workflows (i.e.,uv pip). Now,uv venvwill prompt for confirmation before removing an existing virtual environment. If not in an interactive context, uv will still remove the virtual environment for backwards compatibility. However, this behavior is likely to change in a future release.The behavior for other commands (e.g.,
uv sync) is unchanged.You can opt out of this behavior by setting
UV_VENV_CLEAR=1or passing the--clearflag.Validate that discovered interpreters meet the Python preference (#7934)
uv allows opting out of its managed Python versions with the
--no-managed-pythonandpython-preferenceoptions.Previously, uv would not enforce this option for Python interpreters discovered on the
PATH. For example, if a symlink to a managed Python interpreter was created, uv would allow it to be used even if--no-managed-pythonwas provided. Now, uv ignores Python interpreters that do not match the Python preference unless they are in an active virtual environment or are explicitly requested, e.g., with--python /path/to/python3.13.Similarly, uv would previously not invalidate existing project environments if they did not match the Python preference. Now, uv will invalidate and recreate project environments when the Python preference changes.
You can opt out of this behavior by providing the explicit path to the Python interpreter providing
--managed-python/--no-managed-pythonmatching the interpreter you want.Install dependencies without build systems when they are
pathsources (#14413)When working on a project, uv uses the presence of a build system to determine if it should be built and installed into the environment. However, when a project is a dependency of another project, it can be surprising for the dependency to be missing from the environment.
Previously, uv would not build and install dependencies with
pathsources unless they declared a build system or settool.uv.package = true. Now, dependencies withpathsources are built and installed regardless of the presence of a build system. If a build system is not present, thesetuptools.build_meta:__legacy__backend will be used (per PEP 517).You can opt out of this behavior by setting
package = falsein the source declaration, e.g.:Or, by setting
tool.uv.package = falsein the dependentpyproject.toml.See the documentation on virtual dependencies for details.
Install dependencies without build systems when they are workspace members (#14663)
As described above for dependencies with
pathsources, uv previously would not build and install workspace members that did not declare a build system. Now, uv will build and install workspace members that are a dependency of another workspace member regardless of the presence of a build system. The behavior is unchanged for workspace members that are not included in theproject.dependencies,project.optional-dependencies, ordependency-groupstables of another workspace member.You can opt out of this behavior by setting
tool.uv.package = falsein the workspace member'spyproject.toml.See the documentation on virtual dependencies for details.
Bump
--python-platform linuxtomanylinux_2_28(#14300)uv allows performing platform-specific resolution for explicit targets and provides short aliases, e.g.,
linux, for common targets.Previously, the default target for
--python-platform linuxwasmanylinux_2_17, which is compatible with most Linux distributions from 2014 or newer. We now default tomanylinux_2_28, which is compatible with most Linux distributions from 2019 or newer. This change follows the lead of other tools, such ascibuildwheel, which changed their default tomanylinux_2_28in Mar 2025.This change only affects users requesting a specific target platform. Otherwise, uv detects the
manylinuxtarget from your local glibc version.You can opt out of this behavior by using
--python-platform x86_64-manylinux_2_17instead.Remove
uv versionfallback (#14161)In Apr 2025, uv changed the
uv versioncommand to an interface for viewing and updating the version of the current project. However, when outside a project,uv versionwould continue to display uv's version for backwards compatibility. Now, when used outside of a project,uv versionwill fail.You cannot opt out of this behavior. Use
uv self versioninstead.Require
--globalfor removal of the global Python pin (#14169)Previously,
uv python pin --rmwould allow you to remove the global Python pin without opt in. Now, uv requires the--globalflag to remove the global Python pin.You cannot opt out of this behavior. Use the
--globalflag instead.Support conflicting editable settings across groups (#14197)
Previously, uv would always treat a package as editable if any requirement requested it as editable. However, this prevented users from declaring
pathsources that toggled theeditablesetting across dependency groups. Now, uv allows declaring differenteditablevalues for conflicting groups. However, if a project includes a path dependency twice, once witheditable = trueand once without any editable annotation, those are now considered conflicting, and uv will exit with an error.You cannot opt out of this behavior. Use consistent
editablesettings or mark groups as conflicting.Make
uv_buildthe default build backend inuv init(#14661)The uv build backend (
uv_build) was stabilized in uv 0.7.19. Now, it is the default build backend foruv init --packageanduv init --lib. Previously,hatchlingwas the default build backend. A build backend is still not used without opt-in inuv init, but we expect to change this in a future release.You can opt out of this behavior with
uv init --build-backend hatchling.Set default
UV_TOOL_BIN_DIRon Docker images (#13391)Previously,
UV_TOOL_BIN_DIRwas not set in Docker images which meant thatuv tool installdid not install tools into a directory on thePATHwithout additional configuration. Now,UV_TOOL_BIN_DIRis set to/usr/local/binin all Docker derived images.When the default image user is overridden (e.g.
USER <UID>) with a less privileged user, this may causeuv tool installto fail.You can opt out of this behavior by setting an alternative
UV_TOOL_BIN_DIR.Update
--checkto return an exit code of 1 (#14167)uv uses an exit code of 1 to indicate a "successful failure" and an exit code of 2 to indicate an "error".
Previously,
uv lock --checkanduv sync --checkwould exit with a code of 2 when the lockfile or environment were outdated. Now, uv will exit with a code of 1.You cannot opt out of this behavior.
Use an ephemeral environment for
uv run --withinvocations (#14447)When using
uv run --with, uv layers the requirements requested using--withinto another virtual environment and caches it. Previously, uv would invoke the Python interpreter in this layered environment. However, this allows poisoning the cached environment and introduces race conditions for concurrent invocations. Now, uv will layer another empty virtual environment on top of the cached environment and invoke the Python interpreter there. This should only cause breakage in cases where the environment is being inspected at runtime.You cannot opt out of this behavior.
Restructure the
uv venvcommand output and exit codes (#14546)Previously, uv used
mietteto format theuv venvoutput. However, this was inconsistent with most of the uv CLI. Now, the output is a little different and the exit code has switched from 1 to 2 for some error cases.You cannot opt out of this behavior.
Default to
--workspacewhen adding subdirectories (#14529)When using
uv addto add a subdirectory in a workspace, uv now defaults to adding the target as a workspace member.You can opt out of this behavior by providing
--no-workspace.Add missing validations for disallowed
uv.tomlfields (#14322)uv does not allow some settings in the
uv.toml. Previously, some settings were silently ignored when present in theuv.toml. Now, uv will error.You cannot opt out of this behavior. Use
--no-configor remove the invalid settings.Configuration
v0.7.22Compare Source
Release Notes
Python
See the GraalPy release notes for more details.
Configuration
UV_COMPILE_BYTECODE_TIMEOUTenvironment variable (#14369)cache-controlheaders (#14620)UV_LIBCto override libc selection in multi-libc environment (#14646)Bug fixes
--all-archeswhen paired with--only-downloads(#14629)uv.tomlwhen provided via direct path (#14653)Documentation
revisionin the lockfile versioning doc (#14634)uv cache cleanprior to--reinstall(#14659)Preview features
uv python update-shell(#14627)Install uv 0.7.22
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.7.22
v0.7.21Compare Source
Release Notes
Python
fts4,fts5,rtree, andgeopolyextensions on macOS and LinuxSee the
python-build-standalonerelease notes for more details.Enhancements
--python-platformtouv sync(#14320)uv version --bump(#13578)-wshorthand for--with(#14530)UV_HTTP_RETRIESto customize retry counts (#14544)cache-key(#13438)..) in globs incache-key(#13469)cache-keyperformance (#13469)Preview features
uv sync --output-format json(#13689)Bug fixes
uv toolif it is incompatible with--python(#14606)Documentation
include-group(#14539)setup-python(#14533)Install uv 0.7.21
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
Download uv 0.7.21
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.
baf298d55cto0fd32ab5100fd32ab510to46e80a1b75