From bfedec314b8e1b392e482688d2c21ace33a93707 Mon Sep 17 00:00:00 2001 From: Qwynn Marcelle Date: Sun, 26 Jul 2026 08:46:11 -0400 Subject: [PATCH] fix(ci): point the frozen-source cache at the harnesses' real location MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR #6 wired the parity harnesses into CI and cached .parity-cache — the in-repo default from PR #4. But PR #5 (merged first) moved the harness cache to ~/.cache/workspacejson/cli-parity precisely so the frozen-source clone never trips the architecture guard, and nothing in the workflow sets WORKSPACEJSON_PARITY_CACHE. The cache step therefore saved and restored a directory the harnesses never write: a no-op, with every CI run re-cloning and rebuilding the frozen source from scratch. Point actions/cache at the real default. actions/cache expands ~, and on ubuntu-latest XDG_CACHE_HOME is unset, so the path matches parity-lib.sh's ${XDG_CACHE_HOME:-$HOME/.cache}/workspacejson/cli-parity exactly. The cache key is unchanged — still the immutable frozen-source SHA. --- .github/workflows/ci.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index cb12307..d0b8040 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -81,11 +81,14 @@ jobs: cache: pnpm # The old side is pinned to an immutable commit, so the SHA is a perfect - # cache key — it can never go stale for the wrong reason. + # cache key — it can never go stale for the wrong reason. The path must + # match parity-lib.sh's default: the cache deliberately lives OUTSIDE the + # working tree so the frozen-source clone never trips the architecture + # guard (see PR #5); caching the old in-repo path saved nothing. - name: Restore frozen-source cache uses: actions/cache@v4 with: - path: .parity-cache + path: ~/.cache/workspacejson/cli-parity key: parity-e47eb1b8556c4f361db9a78190a2f36b400756e8-${{ runner.os }}-node22 - run: pnpm install --no-frozen-lockfile