From 9ac252f199a47a45bc31ee12888985a8c135bc8b Mon Sep 17 00:00:00 2001
From: Soulhackzlol <52952716+Soulhackzlol@users.noreply.github.com>
Date: Sun, 7 Jun 2026 19:04:21 +0200
Subject: [PATCH] ci(release): make rust-cache restore-only

The cache-save post-step (tar of a large release target/) is flaky on
Windows runners and red-X'd the release job after the release had already
published. Release builds run on tags, so populating the cache buys
nothing; restore-only keeps future release runs green.
---
 .github/workflows/release.yml | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index c261f3b..03be9d8 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -23,6 +23,11 @@ jobs:
         with:
           components: clippy, rustfmt
       - uses: Swatinem/rust-cache@v2
+        with:
+          # Restore-only: release runs on tags (rare), so populating the cache
+          # buys nothing and the save step is flaky on Windows runners (tar of
+          # a large release target/), which red-X'd the job after publishing.
+          save-if: false
       - name: fmt check
         run: cargo fmt --all -- --check
       - name: clippy
@@ -39,6 +44,11 @@ jobs:
 
       - uses: dtolnay/rust-toolchain@stable
       - uses: Swatinem/rust-cache@v2
+        with:
+          # Restore-only: release runs on tags (rare), so populating the cache
+          # buys nothing and the save step is flaky on Windows runners (tar of
+          # a large release target/), which red-X'd the job after publishing.
+          save-if: false
 
       - name: build release
         run: cargo build --release