From 19be455346d7ef68f8a5e987df9f7f1f2ac741c1 Mon Sep 17 00:00:00 2001 From: Lars Bogner Date: Mon, 27 Jul 2026 14:31:22 +0200 Subject: [PATCH] ci: re-pin UV_CACHE_DIR after setup-uv, which exports its own value regardless of enable-cache 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. --- .gitea/workflows/ci.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.gitea/workflows/ci.yml b/.gitea/workflows/ci.yml index b42c4b2..49b36e7 100644 --- a/.gitea/workflows/ci.yml +++ b/.gitea/workflows/ci.yml @@ -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