goreleaser mit Homebrew, MacPorts, Nix, pacman, zypper, scoop, winget installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• goreleaser

Projektgeschichte

The GitHub repository was created on December 21, 2016, and the project's own anniversary post identifies that date as the first-commit milestone. GoReleaser spent nearly five years in a v0 release stream before the v1.0.0 announcement, where the maintainer described 467 releases and 3299 commits before stabilizing the v1 line.

The project grew from a Go binary release helper into a broader release-engineering system. Official documentation describes a configuration-driven workflow, CI integration from the first commit, generated changelogs, SCM releases, archives, checksums, package-manager publishing, container images, and supply-chain features. By v2, the project framed the major release mainly as cleanup of deprecated options after the v1.26 series.

Adoptionsgeschichte

GoReleaser became closely associated with Go CLI distribution because it solved the recurring package-maintainer chore of producing binaries for many operating systems and publishing them to GitHub Releases, Homebrew taps, Scoop, Docker registries, and other downstream channels. Its README advertises local and CI installation paths, and the Homebrew formula records distribution through Homebrew, MacPorts, Nix, pacman, Scoop, winget, and zypper.

The GoReleaser project also developed an ecosystem around documentation, a GitHub Action, sponsorship, Pro features, examples, and related tools such as nfpm. Later announcements expanded the supported build story beyond Go, including Rust, Zig, TypeScript, Python, Bun, and Deno-oriented release workflows.

Wie es verwendet wird

A typical project keeps a .goreleaser.yaml file in the repository, runs goreleaser init or hand-writes the configuration, validates it with goreleaser check, and lets a CI job run GoReleaser on a release tag. The tool then builds artifacts, archives them, generates changelogs, and publishes them according to the configured release, package, and registry sections.

GoReleaser matters in CI because it encodes release policy in source control. Maintainers can review a single YAML file for binary matrix, archive naming, checksums, signing, Homebrew or Scoop publication, Docker images, and release-note behavior instead of keeping bespoke shell scripts in every repository.

Warum Paket-Nerds sich dafür interessieren

Package nerds care about GoReleaser because it is both a tool and a package-production pattern. It popularized a repeatable path from Git tags to bottled binaries, generated formulas, checksums, SBOM/provenance-related outputs, and package-manager pull updates, reducing the hand-maintained release scripts that often bit-rot in CLI projects.

Its configuration precedence list and schema support are also packaging-significant: editors, CI, and downstream automation can reason about a stable release manifest rather than ad hoc release instructions.

Zeitleiste

• 2016-12-21: Repository created and first-commit anniversary date
• 2021-12-03: v1.0.0 announced after 467 releases and 3299 commits
• 2021-12-21: v1.2 marked five years since the first commit
• 2024-06-04: GoReleaser v2 announced
• 2024-12-15: v2.5 announcement highlighted multi-language support and the eighth anniversary
• 2025-04-29: v2.9 announcement introduced Python builds through Poetry and uv

Related projects

• goreleaser-action runs GoReleaser from GitHub Actions workflows.
• nfpm is a related packaging tool used in the GoReleaser ecosystem.
• Homebrew, Scoop, winget, Docker registries, GitHub Releases, GitLab, and Gitea are common publication targets.
• Cosign and SLSA-related workflows appear in GoReleaser's supply-chain documentation and blog history.

Quellen

• https://github.com/goreleaser/goreleaser
• https://goreleaser.com/blog/goreleaser-v1.2/
• https://goreleaser.com/blog/goreleaser-v1/
• https://goreleaser.com/blog/goreleaser-v2.5/
• https://goreleaser.com/blog/goreleaser-v2.9/
• https://goreleaser.com/blog/goreleaser-v2/
• https://goreleaser.com/customization/
• https://goreleaser.com/customization/ci/
• https://goreleaser.com/customization/publish/scm/