Adolfo Delorenzo
04a5cd2cd3
Some checks failed
ARM64 Build / Build generic ARM64 disk image (push) Has been cancelled
CI / Go Tests (push) Has been cancelled
CI / Build Go Binaries (amd64, linux, linux-amd64) (push) Has been cancelled
CI / Build Go Binaries (arm64, linux, linux-arm64) (push) Has been cancelled
CI / Shellcheck (push) Has been cancelled
The v0.3.1 retag triggered BOTH .gitea/workflows/build-arm64.yaml AND .gitea/workflows/release.yaml. Both build the ARM64 disk image from scratch on the Odroid runner — each kernel build takes ~60 min. The build-arm64 run finished first (uploaded as a workflow artifact, scoped to that run), then release.yaml started another from-scratch build to get the same artifact for the actual Gitea release. That's a wasted hour on a constrained runner. Limit build-arm64.yaml to push-to-main (for early breakage detection) and manual workflow_dispatch. Tag-driven release pipelines are release.yaml's job alone. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>