Files
schemas/.gitea/workflows/goreleaser.yaml
T
argoyleandClaude Opus 5.5 3921de91a6
schemas / vulnerabilities (pull_request) Successful in 3m32s
schemas / check (pull_request) Successful in 5m5s
schemas / check-release (pull_request) Successful in 5m12s
pre-commit / pre-commit (pull_request) Failing after 11m14s
schemas / build (pull_request) Successful in 15m19s
schemas / deploy-prod (pull_request) Skipped
ci: run goreleaser without the runner's GOCACHEPROG
goreleaser runs several go builds at once; each spawns its own gobuildcache,
and they time out on its per-entry file locks while one holds the lock
across a slow S3 call ('failed to acquire lock: context deadline exceeded',
check-release on #997). Use Go's local cache for goreleaser.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ma8eHhW59hLAJuLzBnLvUu
2026-10-07 16:57:18 +02:00

32 lines
749 B
YAML

name: Goreleaser
on:
push:
tags:
- 'v*'
jobs:
release:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
with:
fetch-depth: 0
- uses: actions/setup-node@v7
with:
node-version: '24'
- uses: actions/setup-go@v7
with:
go-version: 'stable'
- name: Install goreleaser
uses: goreleaser/goreleaser-action@v7
with:
version: 'v2.18.2'
install-only: true
- name: Release
run: |
GITEA_TOKEN=$(cat "${RELEASE_TOKEN_FILE}")
export GITEA_TOKEN
# Without GOCACHEPROG: parallel builds contend for gobuildcache's locks.
env -u GOCACHEPROG goreleaser release --clean