fix(ci): pin actions/cache to v4 to unblock Forgejo builds #213

Merged
marco merged 1 commit from fix/pin-cache-v4 into main 2026-07-25 23:12:50 +02:00
Owner

cache@v5+ switched to the cache service v2 (twirp) API, which Forgejo's
built-in Actions cache backend does not implement. Renovate PR #206 bumped
it to v6, after which every job hung on the cache handshake until timeout.
Pin back to v4 (last v1-API release) and cap it in renovate.json so the
bump doesn't return until the runner speaks the v2 API.

Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com

Summary

Screenshots / recording

How it was tested

Checklist

  • just lint passes (CSharpier + analyzers, zero warnings)
  • just test is green
  • The whole solution builds (client and tools included)
  • Multi-platform preserved (server on Win/macOS/Linux, client on Win/macOS)
  • Tests added/updated for this change
  • Linked the related issue (if any) and its Definition of Done is met
cache@v5+ switched to the cache service v2 (twirp) API, which Forgejo's built-in Actions cache backend does not implement. Renovate PR #206 bumped it to v6, after which every job hung on the cache handshake until timeout. Pin back to v4 (last v1-API release) and cap it in renovate.json so the bump doesn't return until the runner speaks the v2 API. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> <!-- Opening this PR with Claude Code (or another assistant)? Before you open it: 1. Ask the author, IN THEIR OWN WORDS, what they changed and why — write it in "Summary". Do not just paraphrase the diff; capture intent. 2. If the change is VISIBLE (UI, gameplay, rendering, a new screen/animation), the assistant PILOTS the client to capture the screenshots — do not ask the author. Start the stack, drive to the scene with the debug harness and `screenshot` each state that shows the feature, then attach the PNGs under "Screenshots / recording" and note the commands you ran. See `docs/debug-harness.md`. Don't open a visible-change PR without them (or a clear note on why the harness can't reach it). 3. Make sure the gates below were actually run locally, then tick the checklist. Delete any section that genuinely doesn't apply. --> ## Summary <!-- What changed and why, in the author's words. --> ## Screenshots / recording <!-- REQUIRED for any visible change (UI / gameplay / rendering). Captured by piloting the client via the debug harness (docs/debug-harness.md) and attached here, with the commands used. Remove this section only if the change has no visible effect. --> ## How it was tested <!-- What you added/ran: new unit tests, `just test`, manual steps to reproduce, etc. --> ## Checklist - [ ] `just lint` passes (CSharpier + analyzers, zero warnings) - [ ] `just test` is green - [ ] The whole solution builds (client and tools included) - [ ] Multi-platform preserved (server on Win/macOS/Linux, client on Win/macOS) - [ ] Tests added/updated for this change - [ ] Linked the related issue (if any) and its Definition of Done is met
fix(ci): pin actions/cache to v4 to unblock Forgejo builds
All checks were successful
ci / Lua content lint (pull_request) Successful in 27s
ci / Lint & Test (pull_request) Successful in 8m22s
2c80dc236f
cache@v5+ switched to the cache service v2 (twirp) API, which Forgejo's
built-in Actions cache backend does not implement. Renovate PR #206 bumped
it to v6, after which every job hung on the cache handshake until timeout.
Pin back to v4 (last v1-API release) and cap it in renovate.json so the
bump doesn't return until the runner speaks the v2 API.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
marco merged commit 108b42c1d3 into main 2026-07-25 23:12:50 +02:00
marco deleted branch fix/pin-cache-v4 2026-07-25 23:12:51 +02:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
marco/IsoMmo!213
No description provided.