fix: release to the Gitea API on its public URL (#997)

goreleaser's gitea_urls.api still pointed at the AWS in-cluster service (gitea-http.gitea.svc.cluster.local), which does not resolve from the Frostmoln runner. Use https://git.unbound.se/api/v1. Also drop RELEASE_TOKEN_FILE=/runner-secrets/release-token (the AWS runner mount); the Frostmoln runner exports RELEASE_TOKEN_FILE itself.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01Ma8eHhW59hLAJuLzBnLvUu
Reviewed-on: #997

.gitea/workflows/ci.yaml

@@ -61,11 +61,15 @@ jobs:
         with:
           version: '~> v2'
           args: check
-      - name: Test release build
+      - name: Install goreleaser
         uses: goreleaser/goreleaser-action@v7
         with:
           version: '~> v2'
-          args: release --snapshot --clean
+          install-only: true
+      # Without the runner's GOCACHEPROG (gobuildcache): goreleaser's parallel
+      # go builds contend for its per-entry locks and time out.
+      - name: Test release build
+        run: env -u GOCACHEPROG goreleaser release --snapshot --clean
 
   build:
     needs: [check, vulnerabilities, check-release]

.gitea/workflows/goreleaser.yaml

@@ -5,9 +5,6 @@ on:
     tags:
       - 'v*'
 
-env:
-  RELEASE_TOKEN_FILE: /runner-secrets/release-token
-
 jobs:
   release:
     runs-on: ubuntu-latest
@@ -30,4 +27,5 @@ jobs:
         run: |
           GITEA_TOKEN=$(cat "${RELEASE_TOKEN_FILE}")
           export GITEA_TOKEN
-          goreleaser release --clean
+          # Without GOCACHEPROG: parallel builds contend for gobuildcache's locks.
+          env -u GOCACHEPROG goreleaser release --clean

.goreleaser.yml

@@ -2,7 +2,7 @@ project_name: unbound-schemas
 version: 2
 
 gitea_urls:
-  api: http://gitea-http.gitea.svc.cluster.local:3000/api/v1
+  api: https://git.unbound.se/api/v1
   download: https://gitea.unbound.se
 
 env: