Release Summary

When running inside GitHub Actions, GoReleaser writes a summary of what your release published to the job summary view, so you can see the outcome of a run without reading its logs.

There is nothing to configure. GoReleaser appends to the file named by the GITHUB_STEP_SUMMARY environment variable, which GitHub Actions sets for every step.

Example

Each notable action becomes one bullet, with a link when there is one:

- Published v1.2.3 to GitHub with 12 assets: https://github.com/user/repo/releases/tag/v1.2.3
- Pushed Docker image `user/foo:v1.2.3`
- Updated homebrew formula `foo.rb` in `user/homebrew-tap`
- Opened pull request to `user/nur` (nixpkg `foo.nix`): https://github.com/user/nur/pull/12
- Pushed `foo` to npm
- Uploaded 8 files to `s3://my-bucket`

What gets reported

GoReleaser reports an action only after it succeeds, so the summary describes what actually happened, not what was configured:

• Releases published to GitHub, GitLab, and Gitea, and milestones closed.
• Homebrew formulas and casks, Scoop manifests, winget packages, krew plugins, and Nix packages, whether GoReleaser pushed them directly or opened a pull request.
• AUR and AUR source packages pushed to their repositories.
• Container images pushed by Docker, Docker v2, and ko, the manifests that reference them, their signatures, and Docker Hub descriptions.
• Packages pushed to npm, Chocolatey, Snapcraft, GemFury, and Cloudsmith.
• Files sent to blob storage and by HTTP upload, including Artifactory.
• Servers published to the MCP registry, Custom Apps published to Iru, and custom publishers that ran.

When nothing is written

GoReleaser writes nothing when GITHUB_STEP_SUMMARY is not set, so runs outside GitHub Actions produce no extra output. The regular logs already cover the same ground.

It also writes nothing when a run publishes nothing, for example goreleaser build, a snapshot release, or a run that only creates a draft release. A draft is not reported as published, because you still have to publish it yourself.