Install

There are two GoReleaser distributions: OSS and Pro, each have a multitude of installation options.

You can see the instructions for each of them below.

Homebrew Tap

OSSPro

brew install goreleaser/tap/goreleaser

brew install goreleaser/tap/goreleaser-pro

Homebrew

OSSPro

brew install goreleaser

Warning

The formula in homebrew-core might be slightly outdated. Use our homebrew tap to always get the latest updates.

Not available.

Snapcraft

OSSPro

sudo snap install --classic goreleaser

Not available.

Scoop

OSSPro

scoop bucket add goreleaser https://github.com/goreleaser/scoop-bucket.git
scoop install goreleaser

scoop bucket add goreleaser https://github.com/goreleaser/scoop-bucket.git
scoop install goreleaser-pro

Apt Repository

OSSPro

echo 'deb [trusted=yes] https://repo.goreleaser.com/apt/ /' | sudo tee /etc/apt/sources.list.d/goreleaser.list
sudo apt update
sudo apt install goreleaser

echo 'deb [trusted=yes] https://repo.goreleaser.com/apt/ /' | sudo tee /etc/apt/sources.list.d/goreleaser.list
sudo apt update
sudo apt install goreleaser-pro

Yum Repository

OSSPro

echo '[goreleaser]
name=GoReleaser
baseurl=https://repo.goreleaser.com/yum/
enabled=1
gpgcheck=0' | sudo tee /etc/yum.repos.d/goreleaser.repo
sudo yum install goreleaser

echo '[goreleaser]
name=GoReleaser
baseurl=https://repo.goreleaser.com/yum/
enabled=1
gpgcheck=0' | sudo tee /etc/yum.repos.d/goreleaser.repo
sudo yum install goreleaser-pro

AUR

OSSPro

yay -S goreleaser-bin

yay -S goreleaser-pro-bin

Nixpkgs

OSSPro

nix-shell -p goreleaser

Warning

The package in nixpkgs might be slightly outdated, as it is not updated automatically. Use our NUR to always get the latest updates.

Not available.

NUR

First, you'll need to add our NUR to your nix configuration. You can follow the guides here.

Once you do that, you can install the packages.

OSSPro

{ pkgs, lib, ... }: {
  home.packages = with pkgs; [
    nur.repos.goreleaser.goreleaser
  ];
}

{ pkgs, lib, ... }: {
  home.packages = with pkgs; [
    nur.repos.goreleaser.goreleaser-pro
  ];
}

Docker

OSSPro

Registries:

• goreleaser/goreleaser
• ghcr.io/goreleaser/goreleaser

Example usage:

docker run --rm --privileged \
  -v $PWD:/go/src/github.com/user/repo \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -w /go/src/github.com/user/repo \
  -e GITHUB_TOKEN \
  -e DOCKER_USERNAME \
  -e DOCKER_PASSWORD \
  -e DOCKER_REGISTRY \
  goreleaser/goreleaser release

Registries:

• goreleaser/goreleaser-pro
• ghcr.io/goreleaser/goreleaser-pro

Example usage:

docker run --rm --privileged \
  -v $PWD:/go/src/github.com/user/repo \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -w /go/src/github.com/user/repo \
  -e GITHUB_TOKEN \
  -e DOCKER_USERNAME \
  -e DOCKER_PASSWORD \
  -e DOCKER_REGISTRY \
  -e GORELEASER_KEY \
  goreleaser/goreleaser-pro release

Warning

The provided docker image does not support the Snapcraft feature.

The DOCKER_REGISTRY environment variable can be left empty when you are releasing to the public docker registry.

If you need more things, you are encouraged to keep your own image. You can always use GoReleaser's own Dockerfile as an example though and iterate from that.

Tip

There are also :nightly tags available with the latest nightly builds.

Linux packages

OSSPro

Download the .deb, .rpm, or .apk packages from the releases page and install them with the appropriate tools.

Download the .deb, .rpm, or .apk packages from the releases page and install them with the appropriate tools.

To install, after downloading the files, run:

dpkg -i goreleaser*.deb
rpm -ivh goreleaser*.rpm
apk add --allow-untrusted goreleaser*.apk

go install

OSSPro

go install github.com/goreleaser/goreleaser/v2@latest

Requires Go 1.22.

Not available.

Bash Script

This script does not install anything, it just downloads, verifies and runs GoReleaser. Its purpose is to be used within scripts and CIs.

OSSPro

curl -sfL https://goreleaser.com/static/run | bash VERSION=v2.1.0 -s -- check

curl -sfL https://goreleaser.com/static/run | DISTRIBUTION=pro VERSION=v2.1.0 bash -s -- check

Tip

The VERSION environment variable can be ommited to get the latest stable version, or you can set it to nightly to get the last nightly build.

Manually

OSSPro

Download the pre-compiled binaries from the releases page and copy them to the desired location.

Download the pre-compiled binaries from the releases page and copy them to the desired location.

Verifying the artifacts

Binaries

All artifacts are checksummed, and the checksum file is signed with cosign.

OSSPro

1. Download the files you want, and the checksums.txt, checksum.txt.pem and checksums.txt.sig files from the releases page:

   wget 'https://github.com/goreleaser/goreleaser/releases/download/v2.1.0/checksums.txt'
   

2. Verify the signature:

   cosign verify-blob \
     --certificate-identity 'https://github.com/goreleaser/goreleaser/.github/workflows/release.yml@refs/tags/v2.1.0' \
     --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
     --cert 'https://github.com/goreleaser/goreleaser/releases/download/v2.1.0/checksums.txt.pem' \
     --signature 'https://github.com/goreleaser/goreleaser/releases/download/v2.1.0/checksums.txt.sig' \
     ./checksums.txt
   

3. If the signature is valid, you can then verify the SHA256 sums match with the downloaded binary:

   sha256sum --ignore-missing -c checksums.txt
   

1. Download the files you want, and the checksums.txt, checksum.txt.pem and checksums.txt.sig files from the releases page:

   wget 'https://github.com/goreleaser/goreleaser-pro/releases/download/v2.1.0-pro/checksums.txt'
   

2. Verify the signature:

   cosign verify-blob \
     --certificate-identity 'https://github.com/goreleaser/goreleaser-pro-internal/.github/workflows/release-pro.yml@refs/tags/v2.1.0-pro' \
     --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
     --cert 'https://github.com/goreleaser/goreleaser-pro/releases/download/v2.1.0-pro/checksums.txt.pem' \
     --signature 'https://github.com/goreleaser/goreleaser-pro/releases/download/v2.1.0-pro/checksums.txt.sig' \
     ./checksums.txt
   

3. If the signature is valid, you can then verify the SHA256 sums match with the downloaded binary:

   sha256sum --ignore-missing -c checksums.txt
   

Docker images

Our Docker images are signed with cosign.

Verify the signatures:

OSSPro

cosign verify \
  --certificate-identity 'https://github.com/goreleaser/goreleaser/.github/workflows/release.yml@refs/tags/v2.1.0' \
  --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
  goreleaser/goreleaser

cosign verify \
  --certificate-identity 'https://github.com/goreleaser/goreleaser-pro-internal/.github/workflows/release-pro.yml@refs/tags/v2.1.0-pro' \
  --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
  goreleaser/goreleaser-pro

Info

The .pem and .sig files are the image name:tag, replacing / and : with -.

Nightly builds

Nightly build are pre-releases of the current code into the main branch. Use it for testing out new features only.

OSSPro

Download the pre-compiled binaries from the nightly release and copy them to the desired location.

Download the pre-compiled binaries from the nightly release and copy them to the desired location.

Docker images are also available, look for tags with a -nightly suffix for the last nightly of a specific release, or the :nightly tag, which is always the latest nightly build available.

You may also use the Bash Script method by setting the VERSION environment variable to nightly.

Packaging status