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

Author: KemingHe

src/assets/uv/_metadata.json

@@ -1,6 +1,6 @@
 {
   "source_repo": "astral-sh/uv",
   "docs_path": "docs",
-  "updated_at": "2025-11-11T22:05:55Z",
-  "commit_sha": "63df2cdfe9017bc3f9575a7efb00ca5fdf9fb289"
+  "updated_at": "2025-11-18T22:05:38Z",
+  "commit_sha": "3ac43e8d15ff93405e305523d3a9abdd7670a627"
 }

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.9.8,<0.10.0"]
+requires = ["uv_build>=0.9.10,<0.10.0"]
 build-backend = "uv_build"
 ```
 

src/assets/uv/concepts/configuration-files.md

@@ -42,13 +42,14 @@ default = true
     `pyproject.toml` files are present in a directory, configuration will be read from `uv.toml`, and
     `[tool.uv]` section in the accompanying `pyproject.toml` will be ignored.
 
-uv will also discover user-level configuration at `~/.config/uv/uv.toml` (or
-`$XDG_CONFIG_HOME/uv/uv.toml`) on macOS and Linux, or `%APPDATA%\uv\uv.toml` on Windows; and
-system-level configuration at `/etc/uv/uv.toml` (or `$XDG_CONFIG_DIRS/uv/uv.toml`) on macOS and
-Linux, or `%SYSTEMDRIVE%\ProgramData\uv\uv.toml` on Windows.
+uv will also discover `uv.toml` configuration files in the user- and system-level
+[configuration directories](../reference/storage.md#configuration-directories), e.g., user-level
+configuration in `~/.config/uv/uv.toml`, and system-level configuration at `/etc/uv/uv.toml` on
+macOS and Linux.
 
-User-and system-level configuration must use the `uv.toml` format, rather than the `pyproject.toml`
-format, as a `pyproject.toml` is intended to define a Python _project_.
+!!! important
+
+    User- and system-level configuration files cannot use the `pyproject.toml` format.
 
 If project-, user-, and system-level configuration files are found, the settings will be merged,
 with project-level configuration taking precedence over the user-level configuration, and user-level

src/assets/uv/concepts/preview.md

@@ -74,6 +74,7 @@ The following preview features are available:
   [system-native location](../concepts/authentication/http.md#the-uv-credentials-store).
 - `workspace-metadata`: Allows using `uv workspace metadata`.
 - `workspace-dir`: Allows using `uv workspace dir`.
+- `workspace-list`: Allows using `uv workspace list`.
 
 ## Disabling preview features
 

src/assets/uv/concepts/projects/init.md

@@ -113,7 +113,7 @@ dependencies = []
 example-pkg = "example_pkg:main"
 
 [build-system]
-requires = ["uv_build>=0.9.8,<0.10.0"]
+requires = ["uv_build>=0.9.10,<0.10.0"]
 build-backend = "uv_build"
 ```
 
@@ -136,7 +136,7 @@ dependencies = []
 example-pkg = "example_pkg:main"
 
 [build-system]
-requires = ["uv_build>=0.9.8,<0.10.0"]
+requires = ["uv_build>=0.9.10,<0.10.0"]
 build-backend = "uv_build"
 ```
 
@@ -197,7 +197,7 @@ requires-python = ">=3.11"
 dependencies = []
 
 [build-system]
-requires = ["uv_build>=0.9.8,<0.10.0"]
+requires = ["uv_build>=0.9.10,<0.10.0"]
 build-backend = "uv_build"
 ```
 

src/assets/uv/concepts/projects/workspaces.md

@@ -75,7 +75,7 @@ bird-feeder = { workspace = true }
 members = ["packages/*"]
 
 [build-system]
-requires = ["uv_build>=0.9.8,<0.10.0"]
+requires = ["uv_build>=0.9.10,<0.10.0"]
 build-backend = "uv_build"
 ```
 
@@ -106,7 +106,7 @@ tqdm = { git = "https://github.com/tqdm/tqdm" }
 members = ["packages/*"]
 
 [build-system]
-requires = ["uv_build>=0.9.8,<0.10.0"]
+requires = ["uv_build>=0.9.10,<0.10.0"]
 build-backend = "uv_build"
 ```
 
@@ -188,7 +188,7 @@ dependencies = ["bird-feeder", "tqdm>=4,<5"]
 bird-feeder = { path = "packages/bird-feeder" }
 
 [build-system]
-requires = ["uv_build>=0.9.8,<0.10.0"]
+requires = ["uv_build>=0.9.10,<0.10.0"]
 build-backend = "uv_build"
 ```
 

src/assets/uv/concepts/python-versions.md

@@ -121,10 +121,15 @@ present, uv will install all the Python versions listed in the file.
     The available Python versions are frozen for each uv release. To install new Python versions,
     you may need upgrade uv.
 
+See the [storage documentation](../reference/storage.md#python-versions) for details about where
+installed Python versions are stored.
+
 ### Installing Python executables
 
-uv installs Python executables into your `PATH` by default, e.g., `uv python install 3.12` will
-install a Python executable into `~/.local/bin`, e.g., as `python3.12`.
+uv installs Python executables into your `PATH` by default, e.g., on Unix `uv python install 3.12`
+will install a Python executable into `~/.local/bin`, e.g., as `python3.12`. See the
+[storage documentation](../reference/storage.md#python-executables) for more details about the
+target directory.
 
 !!! tip
 

src/assets/uv/concepts/tools.md

@@ -35,9 +35,14 @@ treated as disposable, i.e., if you run `uv cache clean` the environment will be
 environment is only cached to reduce the overhead of repeated invocations. If the environment is
 removed, a new one will be created automatically.
 
-When installing a tool with `uv tool install`, a virtual environment is created in the uv tools
-directory. The environment will not be removed unless the tool is uninstalled. If the environment is
-manually deleted, the tool will fail to run.
+When installing a tool with `uv tool install`, a virtual environment is created in the
+[uv tools directory](../reference/storage.md#tools). The environment will not be removed unless the
+tool is uninstalled. If the environment is manually deleted, the tool will fail to run.
+
+!!! important
+
+    Tool environments are _not_ intended to be mutated directly. It is strongly recommended never to
+    mutate a tool environment manually, e.g., with a `pip` operation.
 
 ## Tool versions
 
@@ -109,26 +114,6 @@ $ uv tool install ruff@latest
 $ uv tool install ruff@0.6.0
 ```
 
-## Tools directory
-
-By default, the uv tools directory is named `tools` and is in the uv application state directory,
-e.g., `~/.local/share/uv/tools`. The location may be customized with the `UV_TOOL_DIR` environment
-variable.
-
-To display the path to the tool installation directory:
-
-```console
-$ uv tool dir
-```
-
-Tool environments are placed in a directory with the same name as the tool package, e.g.,
-`.../tools/<name>`.
-
-!!! important
-
-    Tool environments are _not_ intended to be mutated directly. It is strongly recommended never to
-    mutate a tool environment manually, e.g., with a `pip` operation.
-
 ## Upgrading tools
 
 Tool environments may be upgraded via `uv tool upgrade`, or re-created entirely via subsequent
@@ -259,35 +244,23 @@ tool may be unusable.
 ## Tool executables
 
 Tool executables include all console entry points, script entry points, and binary scripts provided
-by a Python package. Tool executables are symlinked into the `bin` directory on Unix and copied on
-Windows.
-
-### The `bin` directory
-
-Executables are installed into the user `bin` directory following the XDG standard, e.g.,
-`~/.local/bin`. Unlike other directory schemes in uv, the XDG standard is used on _all platforms_
-notably including Windows and macOS — there is no clear alternative location to place executables on
-these platforms. The installation directory is determined from the first available environment
-variable:
+by a Python package. Tool executables are symlinked into the
+[executable directory](../reference/storage.md#tool-executables) on Unix and copied on Windows.
 
-- `$UV_TOOL_BIN_DIR`
-- `$XDG_BIN_HOME`
-- `$XDG_DATA_HOME/../bin`
-- `$HOME/.local/bin`
-
-Executables provided by dependencies of tool packages are not installed.
+!!! note
 
-### The `PATH`
+    Executables provided by dependencies of tool packages are not installed.
 
-The `bin` directory must be in the `PATH` variable for tool executables to be available from the
-shell. If it is not in the `PATH`, a warning will be displayed. The `uv tool update-shell` command
-can be used to add the `bin` directory to the `PATH` in common shell configuration files.
+The [executable directory](../reference/storage.md#executable-directory) must be in the `PATH`
+variable for tool executables to be available from the shell. If it is not in the `PATH`, a warning
+will be displayed. The `uv tool update-shell` command can be used to add the executable directory to
+the `PATH` in common shell configuration files.
 
 ### Overwriting executables
 
-Installation of tools will not overwrite executables in the `bin` directory that were not previously
-installed by uv. For example, if `pipx` has been used to install a tool, `uv tool install` will
-fail. The `--force` flag can be used to override this behavior.
+Installation of tools will not overwrite executables in the executable directory that were not
+previously installed by uv. For example, if `pipx` has been used to install a tool,
+`uv tool install` will fail. The `--force` flag can be used to override this behavior.
 
 ## Relationship to `uv run`
 

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.9.8/install.sh | sh
+    $ curl -LsSf https://astral.sh/uv/0.9.10/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.9.8/install.ps1 | iex"
+    PS> powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/0.9.10/install.ps1 | iex"
     ```
 
 !!! tip
@@ -260,7 +260,8 @@ If you need to remove uv from your system, follow these steps:
 
     !!! tip
 
-        Before removing the binaries, you may want to remove any data that uv has stored.
+        Before removing the binaries, you may want to remove any data that uv has stored. See the
+        [storage reference](../reference/storage.md) for details on where uv stores data.
 
 2.  Remove the uv, uvx, and uvw binaries:
 

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.9.8 AS uv
+FROM ghcr.io/astral-sh/uv:0.9.10 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.9.8 AS uv
+FROM ghcr.io/astral-sh/uv:0.9.10 AS uv
 
 # First, bundle the dependencies into the task root.
 FROM public.ecr.aws/lambda/python:3.13 AS builder