GoReleaser

Tag-driven releases for a Go binary with GoReleaser, covering cross-platform builds with version ldflags, archives, checksums, a conventional-commit changelog, a GitHub release workflow, and optional Homebrew publishing.

Category: release

In your existing repository

Ask your agent to check compatibility, follow this fragment’s brief, and verify the resulting project. What happens next

Applies to:: go-cli
Requires tools:: goreleaser

Add to your project

Paste the prompt into the coding agent working on your project.

View prompt

Add the goreleaser fragment to this existing repository. 1. Run npx @steamfield/stacks show goreleaser --json and check that it fits the project. If it does not, explain why before changing files. 2. Run npx @steamfield/stacks add goreleaser and follow the brief it prints. 3. In this repository, run npx @steamfield/stacks verify. Fix failures without weakening or skipping verification steps. 4. Summarize what changed and the verification result. Quote published stats only when they are available, including their interval and sample size. The stacks docs, written for agents, are at https://stacks.steamfield.io/llms.txt.

Or use the terminal

npx @steamfield/stacks add goreleaser

Verify steps
Step	Phase	Layer	Command
release-check	check	check	`make release-check`
release-snapshot	check	build	`make release-snapshot`

Use with a new stack

Starting fresh instead? These stacks support this fragment.

go-clioptional
npx @steamfield/stacks new go-cli --with goreleaser

Files

This fragment supplies instructions rather than project files.

Usage

Among stacks projects in the 28 days through 30 Oct 2026: 845 projects; 66% reached a green verify (62–70%, n=590).

Weekly projects by stack

Projects whose final fragment set included this fragment, grouped by stack.

12 weeksAvailable history

go-cli

go-cli

Stacks projects per UTC week through 30 Oct 2026. Published stack counts only.

Data table

Week ending	Stack	Projects
5 Jul 2026	go-cli	15
12 Jul 2026	go-cli	30
19 Jul 2026	go-cli	30
26 Jul 2026	go-cli	50
2 Aug 2026	go-cli	60
9 Aug 2026	go-cli	55
16 Aug 2026	go-cli	65
23 Aug 2026	go-cli	90
30 Aug 2026	go-cli	65
6 Sept 2026	go-cli	70
13 Sept 2026	go-cli	120
20 Sept 2026	go-cli	130
27 Sept 2026	go-cli	140
4 Oct 2026	go-cli	165
11 Oct 2026	go-cli	205
18 Oct 2026	go-cli	250
25 Oct 2026	go-cli	225

By stack

How often this fragment stays in a default composition, or gets attached as an option.

go-cli

Optional · attached17%

845 projects including the fragment

Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.

Data table

Stack	Projects	Role	Share
go-cli	845	Optional · attached	17%

Green rate with and without it

This compares projects; it isn't an effect of the fragment.

go-cli

With

66%62–70%, n=590

Without

68%66–69%, n=2,840

Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.

Data table

Stack	With	Without
go-cli	66% (62–70%, n=590)	68% (66–69%, n=2,840)

Often used with

Co-occurrence above the baseline, within a stack. Required fragment pairs are excluded.

Not enough runs in this breakdown yet.

Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.

Computed 31 Oct 2026, through 30 Oct 2026. Numbers describe stacks projects, not the ecosystem.