2019-07-17 10:50:58 -04:00
# setup-go
2019-06-19 09:44:17 -04:00
2022-03-31 15:29:52 -04:00
[![build-test ](https://github.com/actions/setup-go/actions/workflows/workflow.yml/badge.svg )](https://github.com/actions/setup-go/actions/workflows/workflow.yml)
[![Validate 'setup-go' ](https://github.com/actions/setup-go/actions/workflows/versions.yml/badge.svg )](https://github.com/actions/setup-go/actions/workflows/versions.yml)
2019-08-12 15:13:31 -04:00
2019-07-17 10:50:58 -04:00
This action sets up a go environment for use in actions by:
2019-06-19 09:44:17 -04:00
2022-03-31 15:29:52 -04:00
- Optionally downloading and caching a version of Go by version and adding to `PATH` .
- Registering problem matchers for error output.
2019-07-17 10:50:58 -04:00
2022-03-25 04:53:28 -04:00
# V3
2020-02-09 14:39:34 -05:00
2022-03-31 15:29:52 -04:00
The V3 edition of the action offers:
- Adds `GOBIN` to the `PATH`
- Proxy support
2022-02-09 06:59:04 -05:00
- Check latest version
2022-03-31 15:29:52 -04:00
- Bug fixes (including issues around version matching and semver)
2020-02-09 14:39:34 -05:00
2022-02-09 06:59:04 -05:00
The action will first check the local cache for a version match. If a version is not found locally, it will pull it from the `main` branch of the [go-versions ](https://github.com/actions/go-versions/blob/main/versions-manifest.json ) repository. On miss or failure, it will fall back to downloading directly from [go dist ](https://storage.googleapis.com/golang ). To change the default behavior, please use the [check-latest input ](#check-latest-version ).
2020-07-20 12:50:40 -04:00
2022-04-20 10:11:14 -04:00
**Note:** The `setup-go` action uses executable binaries which are built by Golang side. The action does not build golang from source code.
2021-12-01 06:10:32 -05:00
Matching by [semver spec ](https://github.com/npm/node-semver ):
2022-03-31 15:29:52 -04:00
2020-02-09 14:39:34 -05:00
```yaml
steps:
2022-03-29 15:16:03 -04:00
- uses: actions/checkout@v3
2022-03-25 04:53:28 -04:00
- uses: actions/setup-go@v3
2021-11-08 05:28:08 -05:00
with:
go-version: '^1.13.1' # The Go version to download (if necessary) and use.
- run: go version
2020-02-09 14:39:34 -05:00
```
2022-03-29 15:16:03 -04:00
```yaml
steps:
- uses: actions/checkout@v3
- uses: actions/setup-go@v3
with:
go-version: '>=1.17.0'
- run: go version
```
2020-02-10 19:18:01 -05:00
Matching an unstable pre-release:
2022-04-01 09:27:16 -04:00
2020-02-10 19:18:01 -05:00
```yaml
steps:
2022-03-29 15:16:03 -04:00
- uses: actions/checkout@v3
- uses: actions/setup-go@v3
with:
go-version: '1.18.0-rc.1' # The Go version to download (if necessary) and use.
- run: go version
```
```yaml
steps:
- uses: actions/checkout@v3
2022-03-25 04:53:28 -04:00
- uses: actions/setup-go@v3
2021-11-08 05:28:08 -05:00
with:
2022-03-29 15:16:03 -04:00
go-version: '1.16.0-beta.1' # The Go version to download (if necessary) and use.
2021-11-08 05:28:08 -05:00
- run: go version
2020-02-10 19:18:01 -05:00
```
2019-07-17 10:50:58 -04:00
# Usage
See [action.yml ](action.yml )
2022-04-01 09:27:16 -04:00
## Basic
2022-03-31 15:29:52 -04:00
2019-07-17 10:50:58 -04:00
```yaml
2019-07-25 21:28:46 -04:00
steps:
2022-03-29 15:16:03 -04:00
- uses: actions/checkout@v3
2022-03-25 04:53:28 -04:00
- uses: actions/setup-go@v3
2022-02-09 06:59:04 -05:00
with:
go-version: '1.16.1' # The Go version to download (if necessary) and use.
- run: go run hello.go
```
2022-04-01 09:27:16 -04:00
## Check latest version
2022-02-09 06:59:04 -05:00
The `check-latest` flag defaults to `false` . Use the default or set `check-latest` to `false` if you prefer stability and if you want to ensure a specific Go version is always used.
If `check-latest` is set to `true` , the action first checks if the cached version is the latest one. If the locally cached version is not the most up-to-date, a Go version will then be downloaded. Set `check-latest` to `true` if you want the most up-to-date Go version to always be used.
> Setting `check-latest` to `true` has performance implications as downloading Go versions is slower than using cached versions.
```yaml
steps:
2022-03-29 15:16:03 -04:00
- uses: actions/checkout@v3
2022-03-25 04:53:28 -04:00
- uses: actions/setup-go@v3
2021-11-08 05:28:08 -05:00
with:
2022-02-09 06:59:04 -05:00
go-version: '1.14'
check-latest: true
2021-11-08 05:28:08 -05:00
- run: go run hello.go
2019-07-17 10:50:58 -04:00
```
2022-05-12 04:04:39 -04:00
## Getting go version from the go.mod file
The `go-version-file` input accepts a path to a `go.mod` file containing the version of Go to be used by a project. As the `go.mod` file contains only major and minor (e.g. 1.18) tags, the action will search for the latest available patch version sequentially in the runner's directory with the cached tools, in the [version-manifest.json ](https://github.com/actions/go-versions/blob/main/versions-manifest.json ) file or at the go servers.
If both the `go-version` and the `go-version-file` inputs are provided then the `go-version` input is used.
> The action will search for the `go.mod` file relative to the repository root
```yaml
steps:
- uses: actions/checkout@v3
- uses: actions/setup-go@v3
with:
go-version-file: 'path/to/go.mod'
- run: go version
```
2019-07-17 10:50:58 -04:00
2022-04-01 09:27:16 -04:00
## Matrix testing
2022-03-31 15:29:52 -04:00
2019-07-17 10:50:58 -04:00
```yaml
jobs:
build:
2022-01-12 01:40:09 -05:00
runs-on: ubuntu-latest
2019-07-17 10:50:58 -04:00
strategy:
matrix:
2020-07-22 07:52:29 -04:00
go: [ '1.14', '1.13' ]
2019-07-17 10:50:58 -04:00
name: Go ${{ matrix.go }} sample
2019-07-25 21:28:46 -04:00
steps:
2022-03-29 15:16:03 -04:00
- uses: actions/checkout@v3
2019-07-17 10:50:58 -04:00
- name: Setup go
2022-03-25 04:53:28 -04:00
uses: actions/setup-go@v3
2019-07-17 10:50:58 -04:00
with:
2019-08-13 16:31:11 -04:00
go-version: ${{ matrix.go }}
2019-07-17 10:50:58 -04:00
- run: go run hello.go
```
2019-06-19 09:44:17 -04:00
2021-12-01 06:10:32 -05:00
### Supported version syntax
2022-03-31 15:29:52 -04:00
2021-12-01 06:10:32 -05:00
The `go-version` input supports the following syntax:
2022-04-01 09:27:16 -04:00
- Specific versions: `1.15` , `1.16.1` , `1.17.0-rc.2` , `1.16.0-beta.1`
- SemVer's version range syntax: `^1.13.1` , `>=1.18.0-rc.1`
For more information about semantic versioning, please refer to [semver ](https://github.com/npm/node-semver ) documentation.
2021-12-01 06:10:32 -05:00
2019-06-19 09:44:17 -04:00
# License
The scripts and documentation in this project are released under the [MIT License ](LICENSE )
# Contributions
2022-04-01 09:27:16 -04:00
Contributions are welcome! See [Contributor's Guide ](docs/contributors.md )
2020-02-09 00:21:39 -05:00
## Code of Conduct
2022-04-01 09:27:16 -04:00
:wave: Be nice. See [our code of conduct ](CONDUCT )