Skip to content

Latest commit

 

History

History
315 lines (236 loc) · 7.98 KB

install.md

File metadata and controls

315 lines (236 loc) · 7.98 KB
Raw

Install

There are two GoReleaser distributions: OSS and Pro.

You can install the pre-compiled binary (in several different ways), use Docker or compile from source (when on OSS).

Below you can find the steps for each of them.

Install the pre-compiled binary

homebrew tap

=== "OSS" sh brew install goreleaser/tap/goreleaser

=== "Pro" sh brew install goreleaser/tap/goreleaser-pro

homebrew

=== "OSS" sh brew install goreleaser

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

snapcraft

=== "OSS" sh sudo snap install --classic goreleaser

scoop

=== "OSS" sh scoop bucket add goreleaser https://github.com/goreleaser/scoop-bucket.git scoop install goreleaser

=== "Pro" sh scoop bucket add goreleaser https://github.com/goreleaser/scoop-bucket.git scoop install goreleaser-pro

apt

=== "OSS" sh 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" sh 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

=== "OSS" sh 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" sh 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

=== "OSS" sh yay -S goreleaser-bin

=== "Pro" sh yay -S goreleaser-pro-bin

deb, rpm and apk packages

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

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

go install

=== "OSS" sh go install github.com/goreleaser/goreleaser@latest

bash script

This might be useful if you need to run it in a CI or Makefile. Note that the script will try to download the latest version, verify its checksums and signagures (if cosign is installed), and run it.

=== "OSS" sh curl -sfL https://goreleaser.com/static/run | bash

=== "Pro" sh curl -sfL https://goreleaser.com/static/run | DISTRIBUTION=pro bash

You can also set a VERSION variable to specify a version instead of using latest.

You can also pass flags and args to GoReleaser:

curl -sfL https://goreleaser.com/static/run |
  VERSION=__VERSION__ DISTRIBUTION=oss bash -s -- check

manually

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

=== "Pro" Download the pre-compiled binaries from the Pro 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.

=== "OSS" 1. Download the files you want, and the checksums.txt, checksum.txt.pem and checksums.txt.sig files from the releases page: sh wget https://github.com/goreleaser/goreleaser/releases/download/__VERSION__/checksums.txt wget https://github.com/goreleaser/goreleaser/releases/download/__VERSION__/checksums.txt.sig wget https://github.com/goreleaser/goreleaser/releases/download/__VERSION__/checksums.txt.pem 1. Verify the signature: sh cosign verify-blob \ --cert checksums.txt.pem \ --signature checksums.txt.sig \ checksums.txt 1. If the signature is valid, you can then verify the SHA256 sums match with the downloaded binary: sh sha256sum --ignore-missing -c checksums.txt

=== "Pro" 1. Download the files you want, and the checksums.txt, checksum.txt.pem and checksums.txt.sig files from the releases page: sh wget https://github.com/goreleaser/goreleaser-pro/releases/download/__VERSION__-pro/checksums.txt wget https://github.com/goreleaser/goreleaser-pro/releases/download/__VERSION__-pro/checksums.txt.sig wget https://github.com/goreleaser/goreleaser-pro/releases/download/__VERSION__-pro/checksums.txt.pem 1. Verify the signature: sh cosign verify-blob \ --cert checksums.txt.pem \ --signature checksums.txt.sig \ checksums.txt 1. If the signature is valid, you can then verify the SHA256 sums match with the downloaded binary: sh sha256sum --ignore-missing -c checksums.txt

docker images

Our Docker images are signed with cosign.

Verify the signatures:

=== "OSS" sh COSIGN_EXPERIMENTAL=1 cosign verify goreleaser/goreleaser

=== "Pro" sh COSIGN_EXPERIMENTAL=1 cosign verify goreleaser/goreleaser-pro

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

Running with Docker

You can also use it within a Docker container. To do that, you'll need to execute something more-or-less like the examples below.

=== "OSS" Registries:

- [`goreleaser/goreleaser`](https://hub.docker.com/r/goreleaser/goreleaser)
- [`ghcr.io/goreleaser/goreleaser`](https://github.com/goreleaser/goreleaser/pkgs/container/goreleaser)

Example usage:

```sh
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
```

=== "Pro" Registries:

- [`goreleaser/goreleaser-pro`](https://hub.docker.com/r/goreleaser/goreleaser-pro)
- [`ghcr.io/goreleaser/goreleaser-pro`](https://github.com/goreleaser/goreleaser/pkgs/container/goreleaser-pro)

Example usage:

```sh
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
```

!!! info Currently, the provided docker image does not support the generation of snapcraft packages.

Note that the image will almost always have the last stable Go version.

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.

Compiling from source

Here you have two options:

If you want to contribute to the project, please follow the steps on our contributing guide.

If you just want to build from source for whatever reason, follow these steps:

clone:

git clone https://github.com/goreleaser/goreleaser
cd goreleaser

get the dependencies:

go mod tidy

build:

go build -o goreleaser .

verify it works:

./goreleaser --version