From 4ea64df14918489a272acae798a22020c8d41231 Mon Sep 17 00:00:00 2001
From: Jeffrie Budde <39542105+JSBtechnologies@users.noreply.github.com>
Date: Wed, 21 Oct 2026 15:27:13 -0500
Subject: [PATCH] fork-release: do not restore target/ from cache

The first tag run restored a target/ cache in which the v8 build script was
fresh but its downloaded static library was absent, and the build failed with
"could not find native static library rusty_v8". A release build is a full
LTO build regardless, so cache only the cargo registry.
---
 .github/workflows/fork-release.yml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/.github/workflows/fork-release.yml b/.github/workflows/fork-release.yml
index 6830b79fe14c..ca11db53de65 100644
--- a/.github/workflows/fork-release.yml
+++ b/.github/workflows/fork-release.yml
@@ -129,10 +129,16 @@ jobs:
           toolchain: 1.99.1
           targets: ${{ matrix.target }}
 
+      # Cache the registry only, never target/. A restored target/ marks the
+      # `v8` build script as fresh while its downloaded static library is not
+      # in the cache, and the build then fails with "could not find native
+      # static library `rusty_v8`" (seen on the first tag run). A release build
+      # is a full LTO build anyway, so the target cache bought almost nothing.
       - uses: Swatinem/rust-cache@v2
         with:
           workspaces: codex-rs
           key: fork-release-${{ matrix.target }}
+          cache-targets: "false"
 
       - name: Stamp fork version into the workspace
         shell: bash