Skip to content

ci(release): build the release binaries without the Go cache - #36

Merged
kristoflemmens merged 1 commit into
mainfrom
ci/release-no-go-cache
Nov 17, 2026
Merged

kristoflemmens merged 1 commit into
mainfrom
ci/release-no-go-cache

Conversation

@kristoflemmens

Copy link
Copy Markdown
Contributor

Why

zizmor (1.32.0) reports a high cache-poisoning finding on actions/setup-go in the binaries job of release.yml. setup-go caches modules and the build cache by default, and restores a cache another run may have written. A release build that restores a poisoned cache would ship it in the signed, attested binaries.

Change

cache: false on that setup-go step. The release build downloads its modules and builds from scratch; it runs once per release, so the extra minute doesn't matter. CI keeps its cache.

zizmor finds nothing after the change; actionlint is clean.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kristoflemmens
kristoflemmens enabled auto-merge (squash) November 17, 2026 08:42
@kristoflemmens
kristoflemmens merged commit 428ba0f into main Nov 17, 2026
12 checks passed
@kristoflemmens
kristoflemmens deleted the ci/release-no-go-cache branch November 17, 2026 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant