ci: re-pin UV_CACHE_DIR after setup-uv, which exports its own value regardless of enable-cache
CI / Format (ruff format) (push) Successful in 1m34s
CI / Lint (ruff check) (push) Successful in 1m43s
CI / Sync project version with tag (push) Has been skipped
CI / Type check (ty) (push) Successful in 45s
CI / Lint (ruff check) (pull_request) Successful in 42s
CI / Format (ruff format) (pull_request) Successful in 45s
CI / Sync project version with tag (pull_request) Has been skipped
CI / Type check (ty) (pull_request) Successful in 47s
CI / Tests (push) Successful in 1m39s
CI / Tests (pull_request) Successful in 1m46s

Log evidence showed setup-uv still sets UV_CACHE_DIR to a tool-cache tmp path
(/tmp/setup-uv-cache) even with enable-cache: false, clobbering the workflow
env pointing at the bind-mounted cache. Re-export it via GITHUB_ENV in a step
right after setup-uv so it wins for the rest of the job.
This commit is contained in:
2026-07-27 14:31:22 +02:00
parent 1787d26d1c
commit 19be455346
+4
View File
@@ -23,6 +23,7 @@ jobs:
- uses: astral-sh/setup-uv@v5
with:
enable-cache: false
- run: echo "UV_CACHE_DIR=/uv-cache" >> "$GITHUB_ENV"
- run: uv sync --extra cpu --extra dev
- run: uv run ruff check .
@@ -38,6 +39,7 @@ jobs:
- uses: astral-sh/setup-uv@v5
with:
enable-cache: false
- run: echo "UV_CACHE_DIR=/uv-cache" >> "$GITHUB_ENV"
- run: uv sync --extra cpu --extra dev
- run: uv run ruff format --check .
@@ -53,6 +55,7 @@ jobs:
- uses: astral-sh/setup-uv@v5
with:
enable-cache: false
- run: echo "UV_CACHE_DIR=/uv-cache" >> "$GITHUB_ENV"
- run: uv sync --extra cpu --extra dev
- run: uv run ty check .
@@ -69,6 +72,7 @@ jobs:
- uses: astral-sh/setup-uv@v5
with:
enable-cache: false
- run: echo "UV_CACHE_DIR=/uv-cache" >> "$GITHUB_ENV"
- run: uv sync --extra cpu --extra dev
- run: uv run pytest