Merge pull request #5: drop cache: setting in setup-go / setup-node

Avoids the zombie reserveCache retries against the unreachable Gitea Actions cache service on :43513. Host-mode runner keeps caches warm in $HOME without needing actions/cache plumbing.

.gitea/workflows/dev-deploy.yaml

@@ -40,7 +40,8 @@ jobs:
         uses: actions/setup-go@v5
         with:
           go-version-file: go.work
-          cache: true
+          # See go-unit.yaml for why `cache: true` is disabled.
+          cache: false
 
       - name: Set up pnpm
         uses: pnpm/action-setup@v4
@@ -51,8 +52,11 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: 22
-          cache: pnpm
-          cache-dependency-path: ui/pnpm-lock.yaml
+          # `cache: pnpm` pushes the pnpm store through the Gitea
+          # Actions cache service which is currently unreachable
+          # (192.168.0.222:43513 ETIMEDOUT). In host-mode the real
+          # store lives in ~/.local/share/pnpm and persists between
+          # jobs without any action plumbing.
 
       - name: Install UI dependencies
         working-directory: ui

.gitea/workflows/go-unit.yaml

@@ -46,7 +46,13 @@ jobs:
         uses: actions/setup-go@v5
         with:
           go-version-file: go.work
-          cache: true
+          # `cache: true` here pushes/pulls archives through the Gitea
+          # Actions cache service at 192.168.0.222:43513. That endpoint
+          # currently does not answer, and the action wastes minutes
+          # per run on reserveCache retries. In host-mode the real
+          # caches live in $HOME (~/go/pkg/mod, ~/.cache/go-build) and
+          # persist between jobs without any actions/cache plumbing.
+          cache: false
 
       - name: Run Go tests
         # client/ is the deprecated Fyne client; excluded from CI per

.gitea/workflows/integration.yaml

@@ -53,7 +53,8 @@ jobs:
         uses: actions/setup-go@v5
         with:
           go-version-file: go.work
-          cache: true
+          # See go-unit.yaml for why `cache: true` is disabled.
+          cache: false
 
       - name: Run integration suite
         # `make integration` precleans leftover docker-compose state and

.gitea/workflows/prod-build.yaml

@@ -37,7 +37,8 @@ jobs:
         uses: actions/setup-go@v5
         with:
           go-version-file: go.work
-          cache: true
+          # See go-unit.yaml for why `cache: true` is disabled.
+          cache: false
 
       - name: Set up pnpm
         uses: pnpm/action-setup@v4
@@ -48,8 +49,7 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: 22
-          cache: pnpm
-          cache-dependency-path: ui/pnpm-lock.yaml
+          # See dev-deploy.yaml for why `cache: pnpm` is disabled.
 
       - name: Resolve image tag
         id: tag

.gitea/workflows/ui-test.yaml

@@ -37,8 +37,11 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: 22
-          cache: pnpm
-          cache-dependency-path: ui/pnpm-lock.yaml
+          # `cache: pnpm` pushes the pnpm store through the Gitea
+          # Actions cache service which is currently unreachable
+          # (192.168.0.222:43513 ETIMEDOUT). In host-mode the real
+          # store lives in ~/.local/share/pnpm and persists between
+          # jobs without any action plumbing.
 
       - name: Install npm dependencies
         working-directory: ui