From 2bce6041d1ec99698a84585113a6ee2ab5c59879 Mon Sep 17 00:00:00 2001
From: Lucas Ramos <3140800+lucas-d-ramos@users.noreply.github.com>
Date: Thu, 29 Oct 2026 19:35:43 +0100
Subject: [PATCH] docker-build: cache input to skip the BuildKit layer cache
 (v14.9.1)

Default true, so existing callers are unchanged. wemove.eu reruns its
660-page prerender on every publish: the cache only spares the ~31s
install, while saving it takes 60-70s (175s after a lockfile change).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---
 .github/workflows/docker-build.yml | 13 +++++++++++--
 README.md                          |  3 +++
 2 files changed, 14 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/docker-build.yml b/.github/workflows/docker-build.yml
index 3a0de18..884d400 100644
--- a/.github/workflows/docker-build.yml
+++ b/.github/workflows/docker-build.yml
@@ -28,6 +28,10 @@ on:
         description: "Name of the production branch"
         type: string
         default: "main"
+      cache:
+        description: "Save and reuse the BuildKit layer cache in the Actions cache"
+        type: boolean
+        default: true
     secrets:
       personal_token:
         description: "Optional personal token used to checkout private repositories (current and submodules)"
@@ -119,5 +123,10 @@ jobs:
           # stages (deps install, compile), which is where the minutes go when
           # the lockfile hasn't changed. Added 2026-10-27 for the Actions
           # budget; without it every release build started from nothing.
-          cache-from: type=gha,scope=${{ inputs.name }}
-          cache-to: type=gha,mode=max,scope=${{ inputs.name }}
+          # `cache: false` skips it where saving costs more than it gives back.
+          # wemove.eu prerenders 660 pages on every publish, so only the install
+          # (~31s) is reused, while saving the cache takes 60-70s (175s when the
+          # lockfile changed). Measured 2026-10-29; on youmove saving takes 15s,
+          # so it keeps the cache.
+          cache-from: ${{ inputs.cache && format('type=gha,scope={0}', inputs.name) || '' }}
+          cache-to: ${{ inputs.cache && format('type=gha,mode=max,scope={0}', inputs.name) || '' }}
diff --git a/README.md b/README.md
index bce06a2..080cc9a 100644
--- a/README.md
+++ b/README.md
@@ -52,6 +52,8 @@ supports staging and production environments via its tagging strategy.
 
 - **production_branch**: The name of the production branch. Default `main`.
 
+- **cache**: Save and reuse the BuildKit layer cache in the caller repo's Actions cache. Default `true`. Set `false` when saving the cache takes longer than it saves: wemove.eu reruns its 660-page prerender on every publish, so only the ~31s install is reused while saving takes 60-70s.
+
 ### Secrets
 
 - **personal_token**: Optional personal access token used to check out private repositories and submodules. Falls back to `github.token` when not provided.
@@ -288,6 +290,7 @@ With a smoke script and a log check (a Next.js frontend in `frontend/`):
 Version tags `v1`–`v13` predate the current scheme and are frozen point releases. The
 floating-major convention (see [`RELEASING.md`](RELEASING.md)) starts at **`v14`**.
 
+- **v14.9.1** — `docker-build.yml`: `cache` input (default `true`). `false` skips the BuildKit layer cache, for callers whose expensive stage reruns on every build; wemove.eu uses it. Existing callers are unaffected.
 - **v14.9** — `docker-build.yml`: BuildKit layer cache in the caller repo's Actions cache (`cache-from`/`cache-to: type=gha`, `mode=max`, scope = image name). A rebuild with an unchanged lockfile reuses the dependency and build stages instead of starting from nothing. No input changes; callers on `@v14` pick it up.
 - **v14.8** — `docker-smoke`: optional `smoke-command` (runs after the probe with `SMOKE_BASE_URL` set; its failure fails the action) and `fail-on-log-pattern` (fails when the container log matches an extended regex). The last 200 lines of the container log are now printed when any step fails, not only the probe. Existing callers are unaffected.
 - **v14.6** — `pin-override` action: a first pass re-resolves every alerted package inside the ranges the tree already declares (`yarn up -R <pkg>`, lockfile only, manifest untouched) before any resolution is written. This is what clears a package installed at several versions, which Dependabot cannot fix, and a fix a hand-closed Dependabot PR taught Dependabot to ignore. Measured across the fleet on 2026-09-11: 220 audit findings to 102. New `bumped` output; `changed` is true when either pass changed something.