chore(deps-dev): Update uv requirement from 0.7.20 to 0.8.0 (#934)

Updates the requirements on [uv](https://github.com/astral-sh/uv) to
permit the latest version.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/astral-sh/uv/releases">uv's
releases</a>.</em></p>
<blockquote>
<h2>0.8.0</h2>
<h2>Release Notes</h2>
<p>Since we released uv <a
href="https://github.com/astral-sh/uv/releases/tag/0.7.0">0.7.0</a> 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.</p>
<p>This release also includes the stabilization of a couple <code>uv
python install</code> features, which have been available under preview
since late last year.</p>
<h3>Breaking changes</h3>
<ul>
<li>
<p><strong>Install Python executables into a directory on the
<code>PATH</code> (<a
href="https://redirect.github.com/astral-sh/uv/pull/14626">#14626</a>)</strong></p>
<p><code>uv python install</code> now installs a versioned Python
executable (e.g., <code>python3.13</code>) into a directory on the
<code>PATH</code> (e.g., <code>~/.local/bin</code>) by default. This
behavior has been available under the <code>--preview</code> flag since
<a href="https://redirect.github.com/astral-sh/uv/pull/8458">Oct
2024</a>. This change should not be breaking unless it shadows a Python
executable elsewhere on the <code>PATH</code>.</p>
<p>To install unversioned executables, i.e., <code>python3</code> and
<code>python</code>, use the <code>--default</code> flag. The
<code>--default</code> flag has also been in preview, but is not
stabilized in this release.</p>
<p>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 <code>uv run python</code>
instead) and you cannot install packages into their environment (use
<code>uvx --with &lt;package&gt; python</code> instead).</p>
<p>As with tool installation, the target directory respects common
variables like <code>XDG_BIN_HOME</code> and can be overridden with a
<code>UV_PYTHON_BIN_DIR</code> variable.</p>
<p>You can opt out of this behavior with <code>uv python install
--no-bin</code> or <code>UV_PYTHON_INSTALL_BIN=0</code>.</p>
<p>See the <a
href="https://docs.astral.sh/uv/concepts/python-versions/#installing-python-executables">documentation
on installing Python executables</a> for more details.</p>
</li>
<li>
<p><strong>Register Python versions with the Windows Registry (<a
href="https://redirect.github.com/astral-sh/uv/pull/14625">#14625</a>)</strong></p>
<p><code>uv python install</code> now registers the installed Python
version with the Windows Registry as specified by <a
href="https://peps.python.org/pep-0514/">PEP 514</a>. This allows using
uv installed Python versions via the <code>py</code> launcher. This
behavior has been available under the <code>--preview</code> flag since
<a href="https://redirect.github.com/astral-sh/uv/pull/10634">Jan
2025</a>. This change should not be breaking, as using the uv Python
versions with <code>py</code> requires explicit opt in.</p>
<p>You can opt out of this behavior with <code>uv python install
--no-registry</code> or <code>UV_PYTHON_INSTALL_REGISTRY=0</code>.</p>
</li>
<li>
<p><strong>Prompt before removing an existing directory in <code>uv
venv</code> (<a
href="https://redirect.github.com/astral-sh/uv/pull/14309">#14309</a>)</strong></p>
<p>Previously, <code>uv venv</code> would remove an existing virtual
environment without confirmation. While this is consistent with the
behavior of project commands (e.g., <code>uv sync</code>), it's
surprising to users that are using imperative workflows (i.e., <code>uv
pip</code>). Now, <code>uv venv</code> will prompt for confirmation
before removing an existing virtual environment. <strong>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.</strong></p>
<p>The behavior for other commands (e.g., <code>uv sync</code>) is
unchanged.</p>
<p>You can opt out of this behavior by setting
<code>UV_VENV_CLEAR=1</code> or passing the <code>--clear</code>
flag.</p>
</li>
<li>
<p><strong>Validate that discovered interpreters meet the Python
preference (<a
href="https://redirect.github.com/astral-sh/uv/pull/7934">#7934</a>)</strong></p>
<p>uv allows opting out of its managed Python versions with the
<code>--no-managed-python</code> and <code>python-preference</code>
options.</p>
<p>Previously, uv would not enforce this option for Python interpreters
discovered on the <code>PATH</code>. For example, if a symlink to a
managed Python interpreter was created, uv would allow it to be used
even if <code>--no-managed-python</code> was provided. Now, uv ignores
Python interpreters that do not match the Python preference
<em>unless</em> they are in an active virtual environment or are
explicitly requested, e.g., with <code>--python
/path/to/python3.13</code>.</p>
<p>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.</p>
<p>You can opt out of this behavior by providing the explicit path to
the Python interpreter providing <code>--managed-python</code> /
<code>--no-managed-python</code> matching the interpreter you want.</p>
</li>
<li>
<p><strong>Install dependencies without build systems when they are
<code>path</code> sources (<a
href="https://redirect.github.com/astral-sh/uv/pull/14413">#14413</a>)</strong></p>
<p>When working on a project, uv uses the <a
href="https://docs.astral.sh/uv/concepts/projects/config/#build-systems">presence
of a build system</a> 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.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/astral-sh/uv/blob/main/CHANGELOG.md">uv's
changelog</a>.</em></p>
<blockquote>
<h2>0.8.0</h2>
<p>Since we released uv <a
href="https://github.com/astral-sh/uv/releases/tag/0.7.0">0.7.0</a> 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.</p>
<p>This release also includes the stabilization of a couple <code>uv
python install</code> features, which have been available under preview
since late last year.</p>
<h3>Breaking changes</h3>
<ul>
<li>
<p><strong>Install Python executables into a directory on the
<code>PATH</code> (<a
href="https://redirect.github.com/astral-sh/uv/pull/14626">#14626</a>)</strong></p>
<p><code>uv python install</code> now installs a versioned Python
executable (e.g., <code>python3.13</code>) into a directory on the
<code>PATH</code> (e.g., <code>~/.local/bin</code>) by default. This
behavior has been available under the <code>--preview</code> flag since
<a href="https://redirect.github.com/astral-sh/uv/pull/8458">Oct
2024</a>. This change should not be breaking unless it shadows a Python
executable elsewhere on the <code>PATH</code>.</p>
<p>To install unversioned executables, i.e., <code>python3</code> and
<code>python</code>, use the <code>--default</code> flag. The
<code>--default</code> flag has also been in preview, but is not
stabilized in this release.</p>
<p>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 <code>uv run python</code>
instead) and you cannot install packages into their environment (use
<code>uvx --with &lt;package&gt; python</code> instead).</p>
<p>As with tool installation, the target directory respects common
variables like <code>XDG_BIN_HOME</code> and can be overridden with a
<code>UV_PYTHON_BIN_DIR</code> variable.</p>
<p>You can opt out of this behavior with <code>uv python install
--no-bin</code> or <code>UV_PYTHON_INSTALL_BIN=0</code>.</p>
<p>See the <a
href="https://docs.astral.sh/uv/concepts/python-versions/#installing-python-executables">documentation
on installing Python executables</a> for more details.</p>
</li>
<li>
<p><strong>Register Python versions with the Windows Registry (<a
href="https://redirect.github.com/astral-sh/uv/pull/14625">#14625</a>)</strong></p>
<p><code>uv python install</code> now registers the installed Python
version with the Windows Registry as specified by <a
href="https://peps.python.org/pep-0514/">PEP 514</a>. This allows using
uv installed Python versions via the <code>py</code> launcher. This
behavior has been available under the <code>--preview</code> flag since
<a href="https://redirect.github.com/astral-sh/uv/pull/10634">Jan
2025</a>. This change should not be breaking, as using the uv Python
versions with <code>py</code> requires explicit opt in.</p>
<p>You can opt out of this behavior with <code>uv python install
--no-registry</code> or <code>UV_PYTHON_INSTALL_REGISTRY=0</code>.</p>
</li>
<li>
<p><strong>Prompt before removing an existing directory in <code>uv
venv</code> (<a
href="https://redirect.github.com/astral-sh/uv/pull/14309">#14309</a>)</strong></p>
<p>Previously, <code>uv venv</code> would remove an existing virtual
environment without confirmation. While this is consistent with the
behavior of project commands (e.g., <code>uv sync</code>), it's
surprising to users that are using imperative workflows (i.e., <code>uv
pip</code>). Now, <code>uv venv</code> will prompt for confirmation
before removing an existing virtual environment. <strong>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.</strong></p>
<p>The behavior for other commands (e.g., <code>uv sync</code>) is
unchanged.</p>
<p>You can opt out of this behavior by setting
<code>UV_VENV_CLEAR=1</code> or passing the <code>--clear</code>
flag.</p>
</li>
<li>
<p><strong>Validate that discovered interpreters meet the Python
preference (<a
href="https://redirect.github.com/astral-sh/uv/pull/7934">#7934</a>)</strong></p>
<p>uv allows opting out of its managed Python versions with the
<code>--no-managed-python</code> and <code>python-preference</code>
options.</p>
<p>Previously, uv would not enforce this option for Python interpreters
discovered on the <code>PATH</code>. For example, if a symlink to a
managed Python interpreter was created, uv would allow it to be used
even if <code>--no-managed-python</code> was provided. Now, uv ignores
Python interpreters that do not match the Python preference
<em>unless</em> they are in an active virtual environment or are
explicitly requested, e.g., with <code>--python
/path/to/python3.13</code>.</p>
<p>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.</p>
<p>You can opt out of this behavior by providing the explicit path to
the Python interpreter providing <code>--managed-python</code> /
<code>--no-managed-python</code> matching the interpreter you want.</p>
</li>
<li>
<p><strong>Install dependencies without build systems when they are
<code>path</code> sources (<a
href="https://redirect.github.com/astral-sh/uv/pull/14413">#14413</a>)</strong></p>
<p>When working on a project, uv uses the <a
href="https://docs.astral.sh/uv/concepts/projects/config/#build-systems">presence
of a build system</a> 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.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/astral-sh/uv/commit/0b23572941e271086485227f7c2b5c440062660f"><code>0b23572</code></a>
Bump version to 0.8.0</li>
<li><a
href="https://github.com/astral-sh/uv/commit/1f887552f6c630c4736ec05cf834086fe95eb92f"><code>1f88755</code></a>
CHANGELOG: manylinux_2_28 is more like 2019 (<a
href="https://redirect.github.com/astral-sh/uv/issues/14696">#14696</a>)</li>
<li><a
href="https://github.com/astral-sh/uv/commit/1a339b76e841188a04af9dbd1ad87136cd301122"><code>1a339b7</code></a>
Add release notes and bump version for 0.8.0 (<a
href="https://redirect.github.com/astral-sh/uv/issues/14690">#14690</a>)</li>
<li><a
href="https://github.com/astral-sh/uv/commit/ac35377132954c9ee0fd60d5a464dab4490966c0"><code>ac35377</code></a>
Fix rendering of <code>uv venv --clear</code> hint in bash (<a
href="https://redirect.github.com/astral-sh/uv/issues/14691">#14691</a>)</li>
<li><a
href="https://github.com/astral-sh/uv/commit/5b716c4e50f2a4e829de3f474125cdac8de11c79"><code>5b716c4</code></a>
Add missing trailing newline to outdated error (<a
href="https://redirect.github.com/astral-sh/uv/issues/14689">#14689</a>)</li>
<li><a
href="https://github.com/astral-sh/uv/commit/cd40a3452295a8d4b6af69206c43282096507c89"><code>cd40a34</code></a>
Build and install workspace members that are dependencies by default (<a
href="https://redirect.github.com/astral-sh/uv/issues/14663">#14663</a>)</li>
<li><a
href="https://github.com/astral-sh/uv/commit/0077f2357f4e016c871b2b651ca59a139a95f19a"><code>0077f23</code></a>
Stabilize addition of Python executables to the bin (<a
href="https://redirect.github.com/astral-sh/uv/issues/14626">#14626</a>)</li>
<li><a
href="https://github.com/astral-sh/uv/commit/ff30f14d50cfdda544397f910808eeec8b20f11b"><code>ff30f14</code></a>
Build <code>path</code> sources without build systems by default (<a
href="https://redirect.github.com/astral-sh/uv/issues/14413">#14413</a>)</li>
<li><a
href="https://github.com/astral-sh/uv/commit/b98ac8c224f651a61ee3c44f6829d70cde80b3a9"><code>b98ac8c</code></a>
Validate that discovered interpreters meet the Python preference (<a
href="https://redirect.github.com/astral-sh/uv/issues/7934">#7934</a>)</li>
<li><a
href="https://github.com/astral-sh/uv/commit/2df06ebfbc2d4df90d47ef9a9e631ba9926712e0"><code>2df06eb</code></a>
Require <code>uv venv --clear</code> before removing an existing
directory (<a
href="https://redirect.github.com/astral-sh/uv/issues/14309">#14309</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/astral-sh/uv/compare/0.7.20...0.8.0">compare
view</a></li>
</ul>
</details>
<br />


Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Author: dependabot[bot]

pyproject.toml

@@ -107,7 +107,7 @@ pip = ">=23.0"
 pipenv = ">=2023.11.5"
 poetry = "^1.7"
 pdm = "^2.11"
-uv = "0.7.20"  # keep pinned to exact version, until a v1.0.0 is released
+uv = "0.8.0"  # keep pinned to exact version, until a v1.0.0 is released