A server-side entry in TopGit's GitHub warehouse: goreleaser/goreleaser-action, 1.0k stars, Backend, TypeScript. GitHub Action for GoReleaser
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
GoReleaser Action runs goreleaser, please follow its docs for
more information about how to customize what GoReleaser does.
Workflow
name: goreleaser
on:
pull_request:
push:
permissions:
contents: write
jobs:
goreleaser:
runs-on: ubuntu-latest
steps:
-
name: Checkout
uses: actions/checkout@v6
with:
fetch-depth: 0
-
name: Set up Go
uses: actions/setup-go@v6
-
name: Run GoReleaser
uses: goreleaser/goreleaser-action@v7
with:
# either 'goreleaser' (default) or 'goreleaser-pro'
distribution: goreleaser
# 'latest', 'nightly', or a semver
version: '~> v2'
args: release --clean
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
# Your GoReleaser Pro key, if you are using the 'goreleaser-pro' distribution
# GORELEASER_KEY: ${{ secrets.GORELEASER_KEY }}
IMPORTANT: note the fetch-depth: 0 input in Checkout step. It is required for the changelog to work correctly.
Verification
The action verifies the integrity of the downloaded GoReleaser archive
against the published checksums.txt automatically — no configuration
required.
If cosign is available on PATH, the
action will additionally verify the cosign sigstore signature of the
checksums file against the GoReleaser release workflow's OIDC identity. If
cosign isn't installed, this step is silently skipped.
Note: cosign signature verification requires GoReleaser v2.13.0 or
newer (and the matching nightly). Earlier releases ship a .sig
detached signature signed with cosign v2, which is not compatible with
the cosign v3 sigstore-bundle format the action verifies. For older
versions the cosign step is silently skipped — only the checksums.txt
SHA-256 verification runs.
Note: when version: nightly is used, the action resolves the
latest immutable vX.Y.Z-<sha>-nightly release from the GitHub
Releases API. Pass GITHUB_TOKEN to the action step (as in the example
above) to avoid unauthenticated API rate limits.
To enable signature verification, install cosign before running the action:
For some events like pull request or schedule you might want to store the artifacts somewhere for testing
purposes. You can do that with the actions/upload-artifact action:
steps:
-
name: Install GoReleaser
uses: goreleaser/goreleaser-action@v7
with:
install-only: true
-
name: Show GoReleaser version
run: goreleaser -v
Cache the binary
The action looks for GoReleaser in the runner tool cache before it
downloads. A second use of the action in the same job, or any job on a
self-hosted runner that already has the version, installs immediately.
A binary taken from the tool cache is not verified again. The cache records
whether checksum or checksum and cosign verification completed. When cosign is
available, the action only reuses a signature-verified entry. A binary whose
checksum could not be verified is used for that invocation but is not cached.
On a self-hosted runner the tool cache is kept between jobs, so it must be
trusted like the runner itself. GitHub-hosted runners start with an empty tool
cache in every job, so they always download and verify.
Customizing
inputs
Following inputs can be used as step.with keys
Name
Type
Default
Description
distribution
String
goreleaser
GoReleaser distribution, either goreleaser or goreleaser-pro
version¹
String
~> v2
GoReleaser version
version-file²
String
Read the GoReleaser version from a file (see below)
args
String
Arguments to pass to GoReleaser
workdir
String
.
Working directory (below repository root)
install-only
Bool
false
Just install GoReleaser
¹ Can be a fixed version like v0.117.0 or a max satisfying semver one like ~> 0.132. In this case this will return v0.132.1.
² Path to a file containing the GoReleaser version. Resolved relative
to workdir. Currently only .tool-versions
(asdf/mise) format is supported. When set, this takes precedence over version.
Following environment variables can be used as step.env keys
Name
Description
GITHUB_TOKEN
GITHUB_TOKEN as provided by secrets and requires contents:write
GORELEASER_KEY
Your GoReleaser Pro License Key, in case you are using the goreleaser-pro distribution
Limitation
GITHUB_TOKEN permissions are limited to the repository
that contains your workflow.
If you need to push the homebrew tap to another repository, you must therefore create a custom Personal Access Token
with repo permissions and add it as a secret in the repository. If you create a
secret named GH_PAT, the step will look like this:
How does goreleaser/goreleaser-action compare to other Backend projects?
goreleaser/goreleaser-action is tracked by TopGit in the Backend category, with 1.0k GitHub stars and written in TypeScript. Browse the Backend topic page on TopGit to compare it against similar projects by stars and activity.
Is goreleaser/goreleaser-action open source?
Yes — goreleaser/goreleaser-action ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/goreleaser/goreleaser-action.
What else is in the Backend space?
goreleaser/goreleaser-action is tracked by TopGit under the Backend category, alongside 5 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What is goreleaser/goreleaser-action?
goreleaser/goreleaser-action (goreleaser/goreleaser-action) is a TypeScript project on GitHub. From the project's own README: GitHub Action for GoReleaser
Where do I read more about goreleaser/goreleaser-action?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/goreleaser/goreleaser-action is the definitive source.
Why is goreleaser/goreleaser-action categorized under Backend?
TopGit places goreleaser/goreleaser-action in the Backend category based on its GitHub topics and description (tagged: "actions", "github-actions", "golang"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Still deciding about goreleaser-action?
One click hands the question to an AI along with this page — see what it says about goreleaser-action.