From 305e1b0ffa9bbaab9bb7be6723ac67035e53cd3e Mon Sep 17 00:00:00 2001
From: cal <cal@manticorum.com>
Date: Wed, 11 Feb 2026 22:12:30 +0000
Subject: [PATCH] ci: switch Docker build cache from type=gha to type=registry

The gha cache backend silently fails on Gitea Actions due to Docker
networking issues between the Buildx builder container and the
act_runner cache server. Registry-based caching stores layers on
Docker Hub, which is more reliable for self-hosted runners.
---
 .gitea/workflows/build.yml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/.gitea/workflows/build.yml b/.gitea/workflows/build.yml
index 95e9863..e71038e 100644
--- a/.gitea/workflows/build.yml
+++ b/.gitea/workflows/build.yml
@@ -194,8 +194,8 @@ jobs:
             manticorum67/paper-dynasty-database:latest
             manticorum67/paper-dynasty-database:v${{ steps.meta.outputs.version }}
             manticorum67/paper-dynasty-database:${{ steps.meta.outputs.version_sha }}
-          cache-from: type=gha
-          cache-to: type=gha,mode=max
+          cache-from: type=registry,ref=manticorum67/paper-dynasty-database:buildcache
+          cache-to: type=registry,ref=manticorum67/paper-dynasty-database:buildcache,mode=max
 
       # ==============================================
       # 7. BUILD SUMMARY
@@ -368,8 +368,8 @@ jobs:
 #    - Check webhook still exists in Discord channel settings
 #
 # 4. Build cache not working
-#    - GitHub Actions cache is stored per repository
-#    - Cache is shared across branches
-#    - May need to clear cache if corrupted
+#    - Uses registry-based caching (pushes cache layers to Docker Hub)
+#    - Requires Docker Hub login to read/write cache
+#    - To clear cache: delete the buildcache tag on Docker Hub
 #
 # ==============================================