From a17c04730f1b8d04bcd05d1c2884e3d52a1a7469 Mon Sep 17 00:00:00 2001
From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com>
Date: Sun, 24 Nov 2024 20:49:09 -0500
Subject: [PATCH] Update documentation references to astral-sh/setup-uv to v4
 (#9408)

---
 docs/guides/integration/github.md | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/docs/guides/integration/github.md b/docs/guides/integration/github.md
index 04c5a0bc2f52..a3259f03be72 100644
--- a/docs/guides/integration/github.md
+++ b/docs/guides/integration/github.md
@@ -20,7 +20,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v3
+        uses: astral-sh/setup-uv@v4
 ```
 
 It is considered best practice to pin to a specific uv version, e.g., with:
@@ -37,7 +37,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v3
+        uses: astral-sh/setup-uv@v4
         with:
           # Install a specific version of uv.
           version: "0.5.4"
@@ -59,7 +59,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v3
+        uses: astral-sh/setup-uv@v4
 
       - name: Set up Python
         run: uv python install
@@ -92,7 +92,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v3
+        uses: astral-sh/setup-uv@v4
 
       - name: Set up Python ${{ matrix.python-version }}
         run: uv python install ${{ matrix.python-version }}
@@ -117,7 +117,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v3
+        uses: astral-sh/setup-uv@v4
 
       - name: "Set up Python"
         uses: actions/setup-python@v5
@@ -140,7 +140,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v3
+        uses: astral-sh/setup-uv@v4
 
       - name: "Set up Python"
         uses: actions/setup-python@v5
@@ -165,7 +165,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v3
+        uses: astral-sh/setup-uv@v4
 
       - name: Set up Python
         run: uv python install
@@ -193,7 +193,7 @@ persisting the cache:
 
 ```yaml title="example.yml"
 - name: Enable caching
-  uses: astral-sh/setup-uv@v3
+  uses: astral-sh/setup-uv@v4
   with:
     enable-cache: true
 ```
@@ -202,7 +202,7 @@ You can configure the action to use a custom cache directory on the runner:
 
 ```yaml title="example.yml"
 - name: Define a custom uv cache path
-  uses: astral-sh/setup-uv@v3
+  uses: astral-sh/setup-uv@v4
   with:
     enable-cache: true
     cache-local-path: "/path/to/cache"
@@ -212,7 +212,7 @@ Or invalidate it when the lockfile changes:
 
 ```yaml title="example.yml"
 - name: Define a cache dependency glob
-  uses: astral-sh/setup-uv@v3
+  uses: astral-sh/setup-uv@v4
   with:
     enable-cache: true
     cache-dependency-glob: "uv.lock"
@@ -222,7 +222,7 @@ Or when any requirements file changes:
 
 ```yaml title="example.yml"
 - name: Define a cache dependency glob
-  uses: astral-sh/setup-uv@v3
+  uses: astral-sh/setup-uv@v4
   with:
     enable-cache: true
     cache-dependency-glob: "requirements**.txt"