From 29911c9ccc5c247fd108f101d8cd419fef590b27 Mon Sep 17 00:00:00 2001 From: Andy Taylor Date: Tue, 4 Aug 2026 15:14:34 +0100 Subject: [PATCH] fix(ci): disable uv cache for release-consistency job The release-consistency job runs only check-release-consistency.py, which is stdlib-only (tomllib/re/argparse) and never invokes uv. No uv cache directory is therefore created. setup-uv v9 fails its post step when told to save a cache path that does not exist on disk: Cache path /home/runner/work/_temp/setup-uv-cache does not exist on disk. The check itself passed; only the cleanup step failed, which still failed the job. This surfaced after bumping setup-uv v4 -> v9 in #5. It passed on that PR's run and failed on the post-merge main run, so it is timing-dependent on whether a cache was restored, not deterministic. Set enable-cache: false for this job only. Every other setup-uv job runs uv sync or uv build and legitimately populates the cache. --- .github/workflows/ci.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 7651c9fe6..8b2a48eeb 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -58,6 +58,10 @@ jobs: - uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0 with: python-version: "3.12" + # This job only runs a stdlib-only script (tomllib/re/argparse); it never + # invokes uv, so no cache directory is ever created. setup-uv v9 errors in + # its post step when asked to save a cache path that does not exist. + enable-cache: false - run: python scripts/check-release-consistency.py test: