-
-
Notifications
You must be signed in to change notification settings - Fork 439
Commit 673bbb4
authored
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?v=4&size=40){kind=avatar}
chore(deps): update all non-major dependencies (#1103)
This PR contains the following updates:
| Package | Type | Update | Change | Age | Confidence |
|---|---|---|---|---|---|
| alpine | final | minor | `3.19` -> `3.22` |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
|
[github.com/alecthomas/repr](https://redirect.github.com/alecthomas/repr)
| require | minor | `v0.4.0` -> `v0.5.1` |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
| [uv](https://redirect.github.com/astral-sh/uv) | | minor | `0.7.19` ->
`0.8.0` |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
---
### Release Notes
<details>
<summary>alecthomas/repr (github.com/alecthomas/repr)</summary>
###
[`v0.5.1`](https://redirect.github.com/alecthomas/repr/compare/v0.5.0...v0.5.1)
[Compare
Source](https://redirect.github.com/alecthomas/repr/compare/v0.5.0...v0.5.1)
###
[`v0.5.0`](https://redirect.github.com/alecthomas/repr/compare/v0.4.0...v0.5.0)
[Compare
Source](https://redirect.github.com/alecthomas/repr/compare/v0.4.0...v0.5.0)
</details>
<details>
<summary>astral-sh/uv (uv)</summary>
###
[`v0.8.0`](https://redirect.github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#080)
[Compare
Source](https://redirect.github.com/astral-sh/uv/compare/0.7.21...0.8.0)
Since we released uv
[0.7.0](https://redirect.github.com/astral-sh/uv/releases/tag/0.5.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
install` features, which have been available under preview since late
last year.
##### Breaking changes
- **Install Python executables into a directory on the `PATH`
([#​14626](https://redirect.github.com/astral-sh/uv/pull/14626))**
`uv python install` now installs a versioned Python executable (e.g.,
`python3.13`) into a directory on the `PATH` (e.g., `~/.local/bin`) by
default. This behavior has been available under the `--preview` flag
since [Oct 2024](https://redirect.github.com/astral-sh/uv/pull/8458).
This change should not be breaking unless it shadows a Python executable
elsewhere on the `PATH`.
To install unversioned executables, i.e., `python3` and `python`, use
the `--default` flag. The `--default` flag 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 python` instead) and
you cannot install packages into their environment (use `uvx --with
<package> python` instead).
As with tool installation, the target directory respects common
variables like `XDG_BIN_HOME` and can be overridden with a
`UV_PYTHON_BIN_DIR` variable.
You can opt out of this behavior with `uv python install --no-bin` or
`UV_PYTHON_INSTALL_BIN=0`.
See the [documentation on installing Python
executables](https://docs.astral.sh/uv/concepts/python-versions/#installing-python-executables)
for more details.
- **Register Python versions with the Windows registry
([#​14625](https://redirect.github.com/astral-sh/uv/pull/14625))**
`uv python install` now registers the installed Python version with the
Windows Registry as specified by [PEP
514](https://peps.python.org/pep-0514/). This allows using uv installed
Python versions via the `py` launcher. This behavior has been available
under the `--preview` flag since [Jan
2025](https://redirect.github.com/astral-sh/uv/pull/10634). This change
should not be breaking, as using the uv Python versions with `py`
requires explicit opt in.
You can opt out of this behavior with `uv python install --no-registry`
or `UV_PYTHON_INSTALL_REGISTRY=0`.
- **Prompt before removing an existing directory in `uv venv`
([#​14309](https://redirect.github.com/astral-sh/uv/pull/14309))**
Previously, `uv venv` would 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 venv` will 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=1` or passing
the `--clear` flag.
- **Validate that discovered interpreters meet the Python preference
([#​7934](https://redirect.github.com/astral-sh/uv/pull/7934))**
uv allows opting out of its managed Python versions with the
`--no-managed-python` and `python-preference` options.
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-python` was 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-python`
matching the interpreter you want.
- **Install dependencies without build systems when they are `path`
sources
([#​14413](https://redirect.github.com/astral-sh/uv/pull/14413))**
When working on a project, uv uses the [presence of a build
system](https://docs.astral.sh/uv/concepts/projects/config/#build-systems)
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 [`path`
sources](https://docs.astral.sh/uv/concepts/projects/dependencies/#path)
unless they declared a build system or set `tool.uv.package = true`.
Now, dependencies with `path` sources are built and installed regardless
of the presence of a build system. If a build system is not present, the
`setuptools.build_meta:__legacy__ ` backend will be used (per [PEP
517](https://peps.python.org/pep-0517/#source-trees)).
You can opt out of this behavior by setting `package = false` in the
source declaration, e.g.:
```toml
[tool.uv.sources]
foo = { path = "./foo", package = false }
```
Or, by setting `tool.uv.package = false` in the dependent
`pyproject.toml`.
See the documentation on [virtual
dependencies](https://docs.astral.sh/uv/concepts/projects/dependencies/#virtual-dependencies)
for details.
- **Install dependencies without build systems when they are workspace
members
([#​14663](https://redirect.github.com/astral-sh/uv/pull/14663))**
As described above for dependencies with `path` sources, 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 the `project.dependencies`,
`project.optional-dependencies`, or `dependency-groups` tables of
another workspace member.
You can opt out of this behavior by setting `tool.uv.package = false` in
the workspace member's `pyproject.toml`.
See the documentation on [virtual
dependencies](https://docs.astral.sh/uv/concepts/projects/dependencies/#virtual-dependencies)
for details.
- **Bump `--python-platform linux` to `manylinux_2_28`
([#​14300](https://redirect.github.com/astral-sh/uv/pull/14300))**
uv allows performing [platform-specific
resolution](https://docs.astral.sh/uv/concepts/resolution/#platform-specific-resolution)
for explicit targets and provides short aliases, e.g., `linux`, for
common targets.
Previously, the default target for `--python-platform linux` was
`manylinux_2_17`, which is compatible with most Linux distributions from
2014 or newer. We now default to `manylinux_2_28`, which is compatible
with most Linux distributions from 2019 or newer. This change follows
the lead of other tools, such as `cibuildwheel`, which changed their
default to `manylinux_2_28` in [Mar
2025](https://redirect.github.com/pypa/cibuildwheel/pull/2330).
This change only affects users requesting a specific target platform.
Otherwise, uv detects the `manylinux` target from your local glibc
version.
You can opt out of this behavior by using `--python-platform
x86_64-manylinux_2_17` instead.
- **Remove `uv version` fallback
([#​14161](https://redirect.github.com/astral-sh/uv/pull/14161))**
In [Apr 2025](https://redirect.github.com/astral-sh/uv/pull/12349), uv
changed the `uv version` command to an interface for viewing and
updating the version of the current project. However, when outside a
project, `uv version` would continue to display uv's version for
backwards compatibility. Now, when used outside of a project, `uv
version` will fail.
You cannot opt out of this behavior. Use `uv self version` instead.
- **Require `--global` for removal of the global Python pin
([#​14169](https://redirect.github.com/astral-sh/uv/pull/14169))**
Previously, `uv python pin --rm` would allow you to remove the global
Python pin without opt in. Now, uv requires the `--global` flag to
remove the global Python pin.
You cannot opt out of this behavior. Use the `--global` flag instead.
- **Support conflicting editable settings across groups
([#​14197](https://redirect.github.com/astral-sh/uv/pull/14197))**
Previously, uv would always treat a package as editable if any
requirement requested it as editable. However, this prevented users from
declaring `path` sources that toggled the `editable` setting across
dependency groups. Now, uv allows declaring different `editable` values
for conflicting groups. However, if a project includes a path dependency
twice, once with `editable = true` and 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 `editable` settings
or [mark groups as
conflicting](https://docs.astral.sh/uv/concepts/projects/config/#conflicting-dependencies).
- **Make `uv_build` the default build backend in `uv init`
([#​14661](https://redirect.github.com/astral-sh/uv/pull/14661))**
The uv build backend (`uv_build`) was [stabilized in uv
0.7.19](https://redirect.github.com/astral-sh/uv/releases/tag/0.7.19).
Now, it is the default build backend for `uv init --package` and `uv
init --lib`. Previously, `hatchling` was the default build backend. A
build backend is still not used without opt-in in `uv 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_DIR` on Docker images
([#​13391](https://redirect.github.com/astral-sh/uv/pull/13391))**
Previously, `UV_TOOL_BIN_DIR` was not set in Docker images which meant
that `uv tool install` did not install tools into a directory on the
`PATH` without additional configuration. Now, `UV_TOOL_BIN_DIR` is set
to `/usr/local/bin` in all Docker derived images.
When the default image user is overridden (e.g. `USER <UID>`) with a
less privileged user, this may cause `uv tool install` to fail.
You can opt out of this behavior by setting an alternative
`UV_TOOL_BIN_DIR`.
- **Update `--check` to return an exit code of 1
([#​14167](https://redirect.github.com/astral-sh/uv/pull/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 --check` and `uv sync --check` would 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 --with` invocations
([#​14447](https://redirect.github.com/astral-sh/uv/pull/14447))**
When using `uv run --with`, uv layers the requirements requested using
`--with` into 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 venv` command output and exit codes
([#​14546](https://redirect.github.com/astral-sh/uv/pull/14546))**
Previously, uv used `miette` to format the `uv venv` output. 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 `--workspace` when adding subdirectories
([#​14529](https://redirect.github.com/astral-sh/uv/pull/14529))**
When using `uv add` to 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.toml` fields
([#​14322](https://redirect.github.com/astral-sh/uv/pull/14322))**
uv does not allow some settings in the `uv.toml`. Previously, some
settings were silently ignored when present in the `uv.toml`. Now, uv
will error.
You cannot opt out of this behavior. Use `--no-config` or remove the
invalid settings.
##### Configuration
- Add support for toggling Python bin and registry install options via
env vars
([#​14662](https://redirect.github.com/astral-sh/uv/pull/14662))
###
[`v0.7.21`](https://redirect.github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0721)
[Compare
Source](https://redirect.github.com/astral-sh/uv/compare/0.7.20...0.7.21)
##### Python
- Restore the SQLite `fts4`, `fts5`, `rtree`, and `geopoly` extensions
on macOS and Linux
See the
[`python-build-standalone` release
notes](https://redirect.github.com/astral-sh/python-build-standalone/releases/tag/20250712)
for more details.
##### Enhancements
- Add `--python-platform` to `uv sync`
([#​14320](https://redirect.github.com/astral-sh/uv/pull/14320))
- Support pre-releases in `uv version --bump`
([#​13578](https://redirect.github.com/astral-sh/uv/pull/13578))
- Add `-w` shorthand for `--with`
([#​14530](https://redirect.github.com/astral-sh/uv/pull/14530))
- Add an exception handler on Windows to display information on crash
([#​14582](https://redirect.github.com/astral-sh/uv/pull/14582))
- Add hint when Python downloads are disabled
([#​14522](https://redirect.github.com/astral-sh/uv/pull/14522))
- Add `UV_HTTP_RETRIES` to customize retry counts
([#​14544](https://redirect.github.com/astral-sh/uv/pull/14544))
- Follow leaf symlinks matched by globs in `cache-key`
([#​13438](https://redirect.github.com/astral-sh/uv/pull/13438))
- Support parent path components (`..`) in globs in `cache-key`
([#​13469](https://redirect.github.com/astral-sh/uv/pull/13469))
- Improve `cache-key` performance
([#​13469](https://redirect.github.com/astral-sh/uv/pull/13469))
##### Preview features
- Add `uv sync --output-format json`
([#​13689](https://redirect.github.com/astral-sh/uv/pull/13689))
##### Bug fixes
- Do not re-resolve with a new Python version in `uv tool` if it is
incompatible with `--python`
([#​14606](https://redirect.github.com/astral-sh/uv/pull/14606))
##### Documentation
- Document how to nest dependency groups with `include-group`
([#​14539](https://redirect.github.com/astral-sh/uv/pull/14539))
- Fix repeated word in Pyodide doc
([#​14554](https://redirect.github.com/astral-sh/uv/pull/14554))
- Update CONTRIBUTING.md with instructions to format Markdown files via
Docker
([#​14246](https://redirect.github.com/astral-sh/uv/pull/14246))
- Fix version number for `setup-python`
([#​14533](https://redirect.github.com/astral-sh/uv/pull/14533))
###
[`v0.7.20`](https://redirect.github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0720)
[Compare
Source](https://redirect.github.com/astral-sh/uv/compare/0.7.19...0.7.20)
##### Python
- Add Python 3.14.0b4
- Add zstd support to Python 3.14 on Unix (it already was available on
Windows)
- Add PyPy 7.3.20 (for Python 3.11.13)
See the [PyPy](https://pypy.org/posts/2025/07/pypy-v7320-release.html)
and
[`python-build-standalone`](https://redirect.github.com/astral-sh/python-build-standalone/releases/tag/20250708)
release notes for more details.
##### Enhancements
- Add `--workspace` flag to `uv add`
([#​14496](https://redirect.github.com/astral-sh/uv/pull/14496))
- Add auto-detection for Intel GPUs
([#​14386](https://redirect.github.com/astral-sh/uv/pull/14386))
- Drop trailing arguments when writing shebangs
([#​14519](https://redirect.github.com/astral-sh/uv/pull/14519))
- Add debug message when skipping Python downloads
([#​14509](https://redirect.github.com/astral-sh/uv/pull/14509))
- Add support for declaring multiple modules in namespace packages
([#​14460](https://redirect.github.com/astral-sh/uv/pull/14460))
##### Bug fixes
- Revert normalization of trailing slashes on index URLs
([#​14511](https://redirect.github.com/astral-sh/uv/pull/14511))
- Fix forced resolution with all extras in `uv version`
([#​14434](https://redirect.github.com/astral-sh/uv/pull/14434))
- Fix handling of pre-releases in preferences
([#​14498](https://redirect.github.com/astral-sh/uv/pull/14498))
- Remove transparent variants in `uv-extract` to enable retries
([#​14450](https://redirect.github.com/astral-sh/uv/pull/14450))
##### Rust API
- Add method to get packages involved in a `NoSolutionError`
([#​14457](https://redirect.github.com/astral-sh/uv/pull/14457))
- Make `ErrorTree` for `NoSolutionError` public
([#​14444](https://redirect.github.com/astral-sh/uv/pull/14444))
##### Documentation
- Finish incomplete sentence in pip migration guide
([#​14432](https://redirect.github.com/astral-sh/uv/pull/14432))
- Remove `cache-dependency-glob` examples for `setup-uv`
([#​14493](https://redirect.github.com/astral-sh/uv/pull/14493))
- Remove `uv pip sync` suggestion with `pyproject.toml`
([#​14510](https://redirect.github.com/astral-sh/uv/pull/14510))
- Update documentation for GitHub to use `setup-uv@v6`
([#​14490](https://redirect.github.com/astral-sh/uv/pull/14490))
</details>
---
### Configuration
📅 **Schedule**: Branch creation - Between 12:00 AM and 03:59 AM, only on
Monday ( * 0-3 * * 1 ) (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.
👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config
help](https://redirect.github.com/renovatebot/renovate/discussions) if
that's undesired.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/alecthomas/chroma).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4yMy4yIiwidXBkYXRlZEluVmVyIjoiNDEuMjMuMiIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6W119-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>1 parent 5d56970 commit 673bbb4Copy full SHA for 673bbb4
File tree
Expand file treeCollapse file tree
6 files changed
+6
-4
lines changedFilter options
- bin
Expand file treeCollapse file tree
6 files changed
+6
-4
lines changed+1-1Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
29 | 29 | | |
30 | 30 | | |
31 | 31 | | |
32 | | - | |
| 32 | + | |
33 | 33 | | |
34 | 34 | | |
35 | 35 | | |
| |||
bin/.uv-0.7.19.pkg renamed to bin/.uv-0.8.0.pkg
Copy file name to clipboardFile renamed without changes.
bin/uv
Copy file name to clipboard+1-1Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | | - | |
| 1 | + | |
bin/uvx
Copy file name to clipboard+1-1Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | | - | |
| 1 | + | |
+1-1Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
7 | | - | |
| 7 | + | |
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
| |||
+2Lines changed: 2 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2 | 2 | | |
3 | 3 | | |
4 | 4 | | |
| 5 | + | |
| 6 | + | |
5 | 7 | | |
6 | 8 | | |
7 | 9 | | |
| |||
0 commit comments