Bump version to 0.6.15 (#13034)

Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>

docs/concepts/projects/layout.md

@@ -82,13 +82,23 @@ explicitly updated using `uv lock`.
 `uv.lock` is a human-readable TOML file but is managed by uv and should not be edited manually. The
 `uv.lock` format is specific to uv and not usable by other tools.
 
-!!! note
+### `pylock.toml`
 
-    Recently Python standardized the lockfile format with `pylock.toml`.
-    For details on the new standard, see [PEP 751](https://peps.python.org/pep-0751/).
+In [PEP 751](https://peps.python.org/pep-0751/), Python standardized a new resolution file format,
+`pylock.toml`.
 
-    Some of uv's functionality cannot be expressed in the `pylock.toml` format,
-    so uv will continue to use the `uv.lock` format.
+`pylock.toml` is a resolution output format intended to replace `requirements.txt` (e.g., in the
+context of `uv pip compile`, whereby a "locked" `requirements.txt` file is generated from a set of
+input requirements). `pylock.toml` is standardized and tool-agnostic, such that in the future,
+`pylock.toml` files generated by uv could be installed by other tools, and vice versa.
 
-    However, support for `pylock.toml` is planned everywhere uv currently supports `requirements.txt` files.
-    For more details and updates on progress, see [12584](https://github.com/astral-sh/uv/issues/12584).
+Some of uv's functionality cannot be expressed in the `pylock.toml` format; as such, uv will
+continue to use the `uv.lock` format within the project interface.
+
+However, uv supports `pylock.toml` as an export target and in the `uv pip` CLI. For example:
+
+- To export a `uv.lock` to the `pylock.toml` format, run: `uv export -o pylock.toml`
+- To generate a `pylock.toml` file from a set of requirements, run:
+  `uv pip compile -o pylock.toml -r requirements.in`
+- To install from a `pylock.toml` file, run: `uv pip sync pylock.toml` or
+  `uv pip install -r pylock.toml`

docs/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.6.14/install.sh | sh
+    $ curl -LsSf https://astral.sh/uv/0.6.15/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:
 
     ```console
-    $ powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/0.6.14/install.ps1 | iex"
+    $ powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/0.6.15/install.ps1 | iex"
     ```
 
 !!! tip

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

docs/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.6.14`
+- `ghcr.io/astral-sh/uv:{major}.{minor}.{patch}`, e.g., `ghcr.io/astral-sh/uv:0.6.15`
 - `ghcr.io/astral-sh/uv:{major}.{minor}`, e.g., `ghcr.io/astral-sh/uv:0.6` (the latest patch
   version)
 
@@ -72,7 +72,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.6.14-alpine`.
+`ghcr.io/astral-sh/uv:{major}.{minor}-{base}`, e.g., `ghcr.io/astral-sh/uv:0.6.15-alpine`.
 
 For more details, see the [GitHub Container](https://github.com/astral-sh/uv/pkgs/container/uv)
 page.
@@ -110,7 +110,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.6.14 /uv /uvx /bin/
+COPY --from=ghcr.io/astral-sh/uv:0.6.15 /uv /uvx /bin/
 ```
 
 !!! tip
@@ -128,7 +128,7 @@ COPY --from=ghcr.io/astral-sh/uv:0.6.14 /uv /uvx /bin/
 Or, with the installer:
 
 ```dockerfile
-ADD https://astral.sh/uv/0.6.14/install.sh /uv-installer.sh
+ADD https://astral.sh/uv/0.6.15/install.sh /uv-installer.sh
 ```
 
 ### Installing a project
@@ -554,5 +554,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.6.14`, or (even better) the specific image digest,
+    version tag, e.g., `ghcr.io/astral-sh/uv:0.6.15`, or (even better) the specific image digest,
     such as `ghcr.io/astral-sh/uv:0.5.27@sha256:5adf09a5a526f380237408032a9308000d14d5947eafa687ad6c6a2476787b4f`.

docs/guides/integration/github.md

@@ -47,7 +47,7 @@ jobs:
         uses: astral-sh/setup-uv@v5
         with:
           # Install a specific version of uv.
-          version: "0.6.14"
+          version: "0.6.15"
 ```
 
 ## Setting up Python

docs/guides/integration/pre-commit.md

@@ -17,7 +17,7 @@ pre-commit, add the following to the `.pre-commit-config.yaml`:
 repos:
   - repo: https://github.com/astral-sh/uv-pre-commit
     # uv version.
-    rev: 0.6.14
+    rev: 0.6.15
     hooks:
       - id: uv-lock
 ```
@@ -28,7 +28,7 @@ To keep your `requirements.txt` file updated using pre-commit:
 repos:
   - repo: https://github.com/astral-sh/uv-pre-commit
     # uv version.
-    rev: 0.6.14
+    rev: 0.6.15
     hooks:
       - id: uv-export
 ```
@@ -39,7 +39,7 @@ To compile requirements via pre-commit, add the following to the `.pre-commit-co
 repos:
   - repo: https://github.com/astral-sh/uv-pre-commit
     # uv version.
-    rev: 0.6.14
+    rev: 0.6.15
     hooks:
       # Compile requirements
       - id: pip-compile
@@ -52,7 +52,7 @@ To compile alternative files, modify `args` and `files`:
 repos:
   - repo: https://github.com/astral-sh/uv-pre-commit
     # uv version.
-    rev: 0.6.14
+    rev: 0.6.15
     hooks:
       # Compile requirements
       - id: pip-compile
@@ -66,7 +66,7 @@ To run the hook over multiple files at the same time:
 repos:
   - repo: https://github.com/astral-sh/uv-pre-commit
     # uv version.
-    rev: 0.6.14
+    rev: 0.6.15
     hooks:
       # Compile requirements
       - id: pip-compile