macOS
brew install goreleaserlocal Homebrew formula metadata
sudo port install goreleaserMacPorts ports tree · devel/goreleaser/Portfile · 来源: api.github.com
安装
brew install goreleaserlocal Homebrew formula metadata
sudo port install goreleaserMacPorts ports tree · devel/goreleaser/Portfile · 来源: api.github.com
nix profile install nixpkgs#goreleasernixpkgs package indexes · pkgs/by-name/go/goreleaser/package.nix · 来源: api.github.com
sudo pacman -S goreleaserArch Linux sync databases · goreleaser · 来源: geo.mirror.pkgbuild.com
sudo zypper install goreleaseropenSUSE Tumbleweed package metadata · goreleaser · 来源: download.opensuse.org
scoop install main/goreleaserScoop official bucket manifest trees · bucket/goreleaser.json · 来源: api.github.com
winget install --id goreleaser.goreleaser -eWindows Package Manager source index · goreleaser.goreleaser · 来源: cdn.winget.microsoft.com
概览
Deliver Go binaries as fast and easily as possible
历史
GoReleaser is a release automation tool that turns tagged source code into cross-platform artifacts, release notes, package-manager updates, container images, checksums, signatures, and CI-driven publishing workflows.
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.
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.
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.
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.
安全态势
narrow executable package without higher-risk signals.
绿色 风险 · 低 置信度 · appliance
在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。
local files
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Config paths the tool may read or write during local use.
.config/goreleaser.yml.config/goreleaser.yaml.goreleaser.yml.goreleaser.yamlgoreleaser.ymlgoreleaser.yaml可执行文件
| 命令 | 类型 | 暴露范围 | 备注 |
|---|---|---|---|
goreleaser | cli | 全局可执行文件 |
新鲜度
这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。
https://github.com/goreleaser/goreleaser
安装元数据
| 软件包键 | brew:goreleaser |
|---|---|
| 版本 | 2.17.0 |
| 软件包管理器 | Homebrew |
| 软件包管理器页面 | https://formulae.brew.sh/formula/goreleaser |
| 主页 | https://goreleaser.com/ |
| 仓库 | https://github.com/goreleaser/goreleaser |
| 上游文档 | https://goreleaser.com/getting-started |
| 许可证 | MIT |
| 源码归档 | https://github.com/goreleaser/goreleaser.git |
| 最后更新 | 2026-07-05T03:37:31Z |
| Pulse | updated |
| 构建依赖 | go |
| Bottle | 可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | 未定义 |
| 服务 | 未声明 |
注册表事实
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | goreleaser |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
源数据库匹配
匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。
goreleaser
nix profile install nixpkgs#goreleasergoreleaser 2.14.0-2
Deliver Go binaries as fast and easily as possible
https://github.com/goreleaser/goreleaser
sudo pacman -S goreleasergoreleaser 2.16.0-1.1
CLI tool for release engineering in Go, Rust, Zig and TypeScript
sudo zypper install goreleasergoreleaser
sudo port install goreleasermain/goreleaser
scoop install main/goreleasergoreleaser.goreleaser
winget install --id goreleaser.goreleaser -e来源线索
此页面由 av-web 从 scripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。
View the package source record on GitHub.