From 00e340591e0ea691b3f84d6e06ee3bfd4c3cdcb1 Mon Sep 17 00:00:00 2001 From: Michael Johnson Date: Fri, 31 Jul 2026 14:56:55 +0100 Subject: [PATCH 1/2] CI: bump actions/checkout v4 -> v7 in the remaining workflows v4 targets Node 20, which the runner already force-upgrades to Node 24 with a deprecation warning on every run. The two image workflows were moved to v7 when they were written; build.yml and the two Claude workflows were left behind. None of the three uses pull_request_target or workflow_run, so v7's fork-checkout block does not apply. --- .github/workflows/build.yml | 2 +- .github/workflows/claude-code-review.yml | 2 +- .github/workflows/claude.yml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index 5204b57..cfa860c 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -15,7 +15,7 @@ jobs: - runner: ubuntu-24.04-arm # linux-aarch64, same arch as the Pi runs-on: ${{ matrix.runner }} steps: - - uses: actions/checkout@v4 + - uses: actions/checkout@v7 with: submodules: recursive diff --git a/.github/workflows/claude-code-review.yml b/.github/workflows/claude-code-review.yml index a3d25d8..fe2a3d8 100644 --- a/.github/workflows/claude-code-review.yml +++ b/.github/workflows/claude-code-review.yml @@ -27,7 +27,7 @@ jobs: steps: - name: Checkout repository - uses: actions/checkout@v4 + uses: actions/checkout@v7 with: fetch-depth: 1 diff --git a/.github/workflows/claude.yml b/.github/workflows/claude.yml index eb9719e..20cbcee 100644 --- a/.github/workflows/claude.yml +++ b/.github/workflows/claude.yml @@ -26,7 +26,7 @@ jobs: actions: read # Required for Claude to read CI results on PRs steps: - name: Checkout repository - uses: actions/checkout@v4 + uses: actions/checkout@v7 with: fetch-depth: 1 From ffd8aaf9ac63cd8f0d310b924fae106b0829b925 Mon Sep 17 00:00:00 2001 From: Michael Johnson Date: Fri, 31 Jul 2026 14:57:16 +0100 Subject: [PATCH 2/2] CI: bump prefix-dev/setup-pixi v0.9.0 -> v0.10.0 Kept separate from the checkout bump because v0.10.0 flips the post-cleanup default to false (prefix-dev/setup-pixi#272), so a cache or build-time regression is attributable to one commit. The default flip is inert here. post-cleanup only deletes .pixi, the pixi binary and the rattler dirs at job end; both versions save the cache from the main step (main.ts), never the post step, so cleanup cannot race it, and these runners are ephemeral GitHub-hosted VMs that are destroyed anyway. Left at the new default rather than pinned back to true. Two real changes do land: the cache is now split into project and global entries, and the project key hashes the pixi binary as well as the lockfile. So the first build after this is a guaranteed cache miss, and subsequent pixi releases invalidate the cache (this repo does not pin a pixi version) -- correct, since a conda env built by a different pixi should not be reused. --- .github/workflows/build.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index cfa860c..11730df 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -19,7 +19,7 @@ jobs: with: submodules: recursive - - uses: prefix-dev/setup-pixi@v0.9.0 + - uses: prefix-dev/setup-pixi@v0.10.0 with: cache: true