docs(src/assets/): update uv official documentation

KemingHe · github-actions[bot] · commit 5d0bd1b954fc · 2025-08-05T22:05:31.000Z
Signed-off-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;
diff --git a/src/assets/uv/_metadata.json b/src/assets/uv/_metadata.json
@@ -1,6 +1,6 @@
 {
   "source_repo": "astral-sh/uv",
   "docs_path": "docs",
-  "updated_at": "2025-07-29T22:05:21Z",
-  "commit_sha": "11fe8f70f9148f96168015777402a764f83ee923"
+  "updated_at": "2025-08-05T22:05:31Z",
+  "commit_sha": "ce37286814dbb802c422f0926487cfab7aefd2b7"
 }
diff --git a/src/assets/uv/concepts/build-backend.md b/src/assets/uv/concepts/build-backend.md
@@ -31,7 +31,7 @@ To use uv as a build backend in an existing project, add `uv_build` to the
 
 ```toml title="pyproject.toml"
 [build-system]
-requires = ["uv_build>=0.8.3,<0.9.0"]
+requires = ["uv_build>=0.8.5,<0.9.0"]
 build-backend = "uv_build"
 ```
 
diff --git a/src/assets/uv/concepts/projects/init.md b/src/assets/uv/concepts/projects/init.md
@@ -111,8 +111,8 @@ dependencies = []
 example-pkg = "example_pkg:main"
 
 [build-system]
-requires = ["hatchling"]
-build-backend = "hatchling.build"
+requires = ["uv_build>=0.8.5,<0.9.0"]
+build-backend = "uv_build"
 ```
 
 !!! tip
@@ -134,8 +134,8 @@ dependencies = []
 example-pkg = "example_pkg:main"
 
 [build-system]
-requires = ["hatchling"]
-build-backend = "hatchling.build"
+requires = ["uv_build>=0.8.5,<0.9.0"]
+build-backend = "uv_build"
 ```
 
 The command can be executed with `uv run`:
@@ -195,8 +195,8 @@ requires-python = ">=3.11"
 dependencies = []
 
 [build-system]
-requires = ["hatchling"]
-build-backend = "hatchling.build"
+requires = ["uv_build>=0.8.5,<0.9.0"]
+build-backend = "uv_build"
 ```
 
 !!! tip
diff --git a/src/assets/uv/concepts/projects/workspaces.md b/src/assets/uv/concepts/projects/workspaces.md
@@ -75,8 +75,8 @@ bird-feeder = { workspace = true }
 members = ["packages/*"]
 
 [build-system]
-requires = ["hatchling"]
-build-backend = "hatchling.build"
+requires = ["uv_build>=0.8.5,<0.9.0"]
+build-backend = "uv_build"
 ```
 
 In this example, the `albatross` project depends on the `bird-feeder` project, which is a member of
@@ -106,8 +106,8 @@ tqdm = { git = "https://github.com/tqdm/tqdm" }
 members = ["packages/*"]
 
 [build-system]
-requires = ["hatchling"]
-build-backend = "hatchling.build"
+requires = ["uv_build>=0.8.5,<0.9.0"]
+build-backend = "uv_build"
 ```
 
 Every workspace member would, by default, install `tqdm` from GitHub, unless a specific member
@@ -188,8 +188,8 @@ dependencies = ["bird-feeder", "tqdm>=4,<5"]
 bird-feeder = { path = "packages/bird-feeder" }
 
 [build-system]
-requires = ["hatchling"]
-build-backend = "hatchling.build"
+requires = ["uv_build>=0.8.5,<0.9.0"]
+build-backend = "uv_build"
 ```
 
 This approach conveys many of the same benefits, but allows for more fine-grained control over
diff --git a/src/assets/uv/concepts/tools.md b/src/assets/uv/concepts/tools.md
@@ -209,6 +209,40 @@ $ uvx -w <extra-package> <tool-package>
 If the requested version conflicts with the requirements of the tool package, package resolution
 will fail and the command will error.
 
+## Installing executables from additional packages
+
+When installing a tool, you may want to include executables from additional packages in the same
+tool environment. This is useful when you have related tools that work together or when you want to
+install multiple executables that share dependencies.
+
+The `--with-executables-from` option allows you to specify additional packages whose executables
+should be installed alongside the main tool:
+
+```console
+$ uv tool install --with-executables-from <package1>,<package2> <tool-package>
+```
+
+For example, to install Ansible along with executables from `ansible-core` and `ansible-lint`:
+
+```console
+$ uv tool install --with-executables-from ansible-core,ansible-lint ansible
+```
+
+This will install all executables from the `ansible`, `ansible-core`, and `ansible-lint` packages
+into the same tool environment, making them all available on the `PATH`.
+
+The `--with-executables-from` option can be combined with other installation options:
+
+```console
+$ uv tool install --with-executables-from ansible-core --with mkdocs-material ansible
+```
+
+Note that `--with-executables-from` differs from `--with` in that:
+
+- `--with` includes additional packages as dependencies but does not install their executables
+- `--with-executables-from` includes both the packages as dependencies and installs their
+  executables
+
 ## Python versions
 
 Each tool environment is linked to a specific Python version. This uses the same Python version
diff --git a/src/assets/uv/getting-started/installation.md b/src/assets/uv/getting-started/installation.md
@@ -25,7 +25,7 @@ uv provides a standalone installer to download and install uv:
     Request a specific version by including it in the URL:
 
     ```console
-    $ curl -LsSf https://astral.sh/uv/0.8.3/install.sh | sh
+    $ curl -LsSf https://astral.sh/uv/0.8.5/install.sh | sh
     ```
 
 === "Windows"
@@ -41,7 +41,7 @@ uv provides a standalone installer to download and install uv:
     Request a specific version by including it in the URL:
 
     ```pwsh-session
-    PS> powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/0.8.3/install.ps1 | iex"
+    PS> powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/0.8.5/install.ps1 | iex"
     ```
 
 !!! tip
@@ -151,7 +151,7 @@ $ uv self update
 !!! tip
 
     Updating uv will re-run the installer and can modify your shell profiles. To disable this
-    behavior, set `INSTALLER_NO_MODIFY_PATH=1`.
+    behavior, set `UV_NO_MODIFY_PATH=1`.
 
 When another installation method is used, self-updates are disabled. Use the package manager's
 upgrade method instead. For example, with `pip`:
diff --git a/src/assets/uv/guides/integration/aws-lambda.md b/src/assets/uv/guides/integration/aws-lambda.md
@@ -92,7 +92,7 @@ the second stage, we'll copy this directory over to the final image, omitting th
 other unnecessary files.
 
 ```dockerfile title="Dockerfile"
-FROM ghcr.io/astral-sh/uv:0.8.3 AS uv
+FROM ghcr.io/astral-sh/uv:0.8.5 AS uv
 
 # First, bundle the dependencies into the task root.
 FROM public.ecr.aws/lambda/python:3.13 AS builder
@@ -334,7 +334,7 @@ And confirm that opening http://127.0.0.1:8000/ in a web browser displays, "Hell
 Finally, we'll update the Dockerfile to include the local library in the deployment package:
 
 ```dockerfile title="Dockerfile"
-FROM ghcr.io/astral-sh/uv:0.8.3 AS uv
+FROM ghcr.io/astral-sh/uv:0.8.5 AS uv
 
 # First, bundle the dependencies into the task root.
 FROM public.ecr.aws/lambda/python:3.13 AS builder
diff --git a/src/assets/uv/guides/integration/docker.md b/src/assets/uv/guides/integration/docker.md
@@ -31,7 +31,7 @@ $ docker run --rm -it ghcr.io/astral-sh/uv:debian uv --help
 The following distroless images are available:
 
 - `ghcr.io/astral-sh/uv:latest`
-- `ghcr.io/astral-sh/uv:{major}.{minor}.{patch}`, e.g., `ghcr.io/astral-sh/uv:0.8.3`
+- `ghcr.io/astral-sh/uv:{major}.{minor}.{patch}`, e.g., `ghcr.io/astral-sh/uv:0.8.5`
 - `ghcr.io/astral-sh/uv:{major}.{minor}`, e.g., `ghcr.io/astral-sh/uv:0.8` (the latest patch
   version)
 
@@ -75,7 +75,7 @@ And the following derived images are available:
 
 As with the distroless image, each derived image is published with uv version tags as
 `ghcr.io/astral-sh/uv:{major}.{minor}.{patch}-{base}` and
-`ghcr.io/astral-sh/uv:{major}.{minor}-{base}`, e.g., `ghcr.io/astral-sh/uv:0.8.3-alpine`.
+`ghcr.io/astral-sh/uv:{major}.{minor}-{base}`, e.g., `ghcr.io/astral-sh/uv:0.8.5-alpine`.
 
 In addition, starting with `0.8` each derived image also sets `UV_TOOL_BIN_DIR` to `/usr/local/bin`
 to allow `uv tool install` to work as expected with the default user.
@@ -116,7 +116,7 @@ Note this requires `curl` to be available.
 In either case, it is best practice to pin to a specific uv version, e.g., with:
 
 ```dockerfile
-COPY --from=ghcr.io/astral-sh/uv:0.8.3 /uv /uvx /bin/
+COPY --from=ghcr.io/astral-sh/uv:0.8.5 /uv /uvx /bin/
 ```
 
 !!! tip
@@ -134,7 +134,7 @@ COPY --from=ghcr.io/astral-sh/uv:0.8.3 /uv /uvx /bin/
 Or, with the installer:
 
 ```dockerfile
-ADD https://astral.sh/uv/0.8.3/install.sh /uv-installer.sh
+ADD https://astral.sh/uv/0.8.5/install.sh /uv-installer.sh
 ```
 
 ### Installing a project
@@ -560,5 +560,5 @@ Verified OK
 !!! tip
 
     These examples use `latest`, but best practice is to verify the attestation for a specific
-    version tag, e.g., `ghcr.io/astral-sh/uv:0.8.3`, or (even better) the specific image digest,
+    version tag, e.g., `ghcr.io/astral-sh/uv:0.8.5`, or (even better) the specific image digest,
     such as `ghcr.io/astral-sh/uv:0.5.27@sha256:5adf09a5a526f380237408032a9308000d14d5947eafa687ad6c6a2476787b4f`.
diff --git a/src/assets/uv/guides/integration/github.md b/src/assets/uv/guides/integration/github.md
@@ -47,7 +47,7 @@ jobs:
         uses: astral-sh/setup-uv@v6
         with:
           # Install a specific version of uv.
-          version: "0.8.3"
+          version: "0.8.5"
 ```
 
 ## Setting up Python
diff --git a/src/assets/uv/guides/integration/pre-commit.md b/src/assets/uv/guides/integration/pre-commit.md
@@ -19,7 +19,7 @@ To make sure your `uv.lock` file is up to date even if your `pyproject.toml` fil
 repos:
   - repo: https://github.com/astral-sh/uv-pre-commit
     # uv version.
-    rev: 0.8.3
+    rev: 0.8.5
     hooks:
       - id: uv-lock
 ```
@@ -30,7 +30,7 @@ To keep a `requirements.txt` file in sync with your `uv.lock` file:
 repos:
   - repo: https://github.com/astral-sh/uv-pre-commit
     # uv version.
-    rev: 0.8.3
+    rev: 0.8.5
     hooks:
       - id: uv-export
 ```
@@ -41,7 +41,7 @@ To compile requirements files:
 repos:
   - repo: https://github.com/astral-sh/uv-pre-commit
     # uv version.
-    rev: 0.8.3
+    rev: 0.8.5
     hooks:
       # Compile requirements
       - id: pip-compile
@@ -54,7 +54,7 @@ To compile alternative requirements files, modify `args` and `files`:
 repos:
   - repo: https://github.com/astral-sh/uv-pre-commit
     # uv version.
-    rev: 0.8.3
+    rev: 0.8.5
     hooks:
       # Compile requirements
       - id: pip-compile
@@ -68,7 +68,7 @@ To run the hook over multiple files at the same time, add additional entries:
 repos:
   - repo: https://github.com/astral-sh/uv-pre-commit
     # uv version.
-    rev: 0.8.3
+    rev: 0.8.5
     hooks:
       # Compile requirements
       - id: pip-compile
diff --git a/src/assets/uv/guides/tools.md b/src/assets/uv/guides/tools.md
@@ -213,6 +213,14 @@ As with `uvx`, installations can include additional packages:
 $ uv tool install mkdocs --with mkdocs-material
 ```
 
+Multiple related executables can be installed together in the same tool environment, using the
+`--with-executables-from` flag. For example, the following will install the executables from
+`ansible`, plus those ones provided by `ansible-core` and `ansible-lint`:
+
+```console
+$ uv tool install --with-executables-from ansible-core,ansible-lint ansible
+```
+
 ## Upgrading tools
 
 To upgrade a tool, use `uv tool upgrade`:
diff --git a/src/assets/uv/reference/cli.md b/src/assets/uv/reference/cli.md
@@ -2198,6 +2198,7 @@ uv tool install [OPTIONS] <PACKAGE>
 <p>You can configure fine-grained logging using the <code>RUST_LOG</code> environment variable. (<a href="https://docs.rs/tracing-subscriber/latest/tracing_subscriber/filter/struct.EnvFilter.html#directives">https://docs.rs/tracing-subscriber/latest/tracing_subscriber/filter/struct.EnvFilter.html#directives</a>)</p>
 </dd><dt id="uv-tool-install--with"><a href="#uv-tool-install--with"><code>--with</code></a>, <code>-w</code> <i>with</i></dt><dd><p>Include the following additional requirements</p>
 </dd><dt id="uv-tool-install--with-editable"><a href="#uv-tool-install--with-editable"><code>--with-editable</code></a> <i>with-editable</i></dt><dd><p>Include the given packages in editable mode</p>
+</dd><dt id="uv-tool-install--with-executables-from"><a href="#uv-tool-install--with-executables-from"><code>--with-executables-from</code></a> <i>with-executables-from</i></dt><dd><p>Install executables from the following packages</p>
 </dd><dt id="uv-tool-install--with-requirements"><a href="#uv-tool-install--with-requirements"><code>--with-requirements</code></a> <i>with-requirements</i></dt><dd><p>Include all requirements listed in the given <code>requirements.txt</code> files</p>
 </dd></dl>
 
diff --git a/src/assets/uv/reference/environment.md b/src/assets/uv/reference/environment.md
@@ -68,6 +68,12 @@ script, to include the name of the wrapper script in the output file.
 Equivalent to the `--default-index` command-line argument. If set, uv will use
 this URL as the default index when searching for packages.
 
+### `UV_DOWNLOAD_URL`
+
+The URL from which to download uv using the standalone installer. By default, installs from
+uv's GitHub Releases. `INSTALLER_DOWNLOAD_URL` is also supported as an alias, for backwards
+compatibility.
+
 ### `UV_ENV_FILE`
 
 `.env` files from which to load environment variables when executing `uv run` commands.
@@ -269,6 +275,12 @@ Skip writing `uv` installer metadata files (e.g., `INSTALLER`, `REQUESTED`, and
 
 Disable use of uv-managed Python versions.
 
+### `UV_NO_MODIFY_PATH`
+
+Avoid modifying the `PATH` environment variable when installing uv using the standalone
+installer and `self update` feature. `INSTALLER_NO_MODIFY_PATH` is also supported as an
+alias, for backwards compatibility.
+
 ### `UV_NO_PROGRESS`
 
 Equivalent to the `--no-progress` command-line argument. Disables all progress output. For
@@ -562,11 +574,6 @@ Proxy for HTTP requests.
 
 Timeout (in seconds) for HTTP requests. Equivalent to `UV_HTTP_TIMEOUT`.
 
-### `INSTALLER_NO_MODIFY_PATH`
-
-Avoid modifying the `PATH` environment variable when installing uv using the standalone
-installer and `self update` feature.
-
 ### `JPY_SESSION_NAME`
 
 Used to detect when running inside a Jupyter notebook.
diff --git a/src/assets/uv/reference/installer.md b/src/assets/uv/reference/installer.md
@@ -23,14 +23,14 @@ To change the installation path, use `UV_INSTALL_DIR`:
 ## Disabling shell modifications
 
 The installer may also update your shell profiles to ensure the uv binary is on your `PATH`. To
-disable this behavior, use `INSTALLER_NO_MODIFY_PATH`. For example:
+disable this behavior, use `UV_NO_MODIFY_PATH`. For example:
 
 ```console
-$ curl -LsSf https://astral.sh/uv/install.sh | env INSTALLER_NO_MODIFY_PATH=1 sh
+$ curl -LsSf https://astral.sh/uv/install.sh | env UV_NO_MODIFY_PATH=1 sh
 ```
 
-If installed with `INSTALLER_NO_MODIFY_PATH`, subsequent operations, like `uv self update`, will not
-modify your shell profiles.
+If installed with `UV_NO_MODIFY_PATH`, subsequent operations, like `uv self update`, will not modify
+your shell profiles.
 
 ## Unmanaged installations
 
diff --git a/src/assets/uv/reference/settings.md b/src/assets/uv/reference/settings.md

Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"source_repo": "astral-sh/uv",`
`3`	`3`	`"docs_path": "docs",`
`4`		`- "updated_at": "2025-07-29T22:05:21Z",`
`5`		`- "commit_sha": "11fe8f70f9148f96168015777402a764f83ee923"`
	`4`	`+ "updated_at": "2025-08-05T22:05:31Z",`
	`5`	`+ "commit_sha": "ce37286814dbb802c422f0926487cfab7aefd2b7"`
`6`	`6`	`}`