ci: fix goreleaser build cache misses on release#2915
Merged
matiasinsaurralde merged 1 commit intoMar 22, 2026
Merged
Conversation
actions/setup-go saves and restores the build cache keyed with the active environment. Without CGO_ENABLED=0 set at the job level, the cache is saved with CGO_ENABLED=1 (Linux default), but goreleaser builds with CGO_ENABLED=0, causing a full recompile of all packages on every release run despite a reported cache hit. Signed-off-by: Matías Insaurralde <matias@chainloop.dev>
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
migmartri
approved these changes
Mar 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The release job was doing a full recompile of all binaries on every run despite
actions/setup-goreporting a cache hit. The root cause:CGO_ENABLED=0was only set inside.goreleaser.yml, not at the job level, so the build cache was saved and restored withCGO_ENABLED=1(the Linux default). Goreleaser then built withCGO_ENABLED=0, producing different build cache keys for every package in the tree.Setting
CGO_ENABLED=0at the job level aligns the cache key with what goreleaser uses. On warm cache runs, only packages whose source actually changed will recompile.