Support for caching dependency files and compiler's build outputs

This release introduces support for caching dependency files and compiler's build outputs #228. For that action uses @toolkit/cache library under the hood that in turn allows getting rid of configuring @actions/cache action separately and simplifies the whole workflow.

Such input parameters as cache and cache-dependency-path were added. The cache input is optional, and caching is turned off by default, cache-dependency-path is used to specify the path to a dependency file - go.sum.

Examples of use-cases:

• cache input only:

steps:
- uses: actions/checkout@v3
- uses: actions/setup-go@v3
  with:
    go-version: '18'
    cache: true

• cache along with cache-dependency-path:

steps:
- uses: actions/checkout@v3
- uses: actions/setup-go@v3
  with:
    go-version: '18'
    cache: true
    cache-dependency-path: subdir/go.sum

Add go-version-file input

Adding Go version file support

In scope of this release we add the go-version-file input. The new input (go-version-file) provides functionality to specify the path to the file containing Go version with such behaviour:

• If the file does not exist the action will throw an error.
• If you specify both go-version and go-version-file inputs, the action will use value from the go-version input and throw the following warning: Both go-version and go-version-file inputs are specified, only go-version will be used.
• For now the action supports .go-version and go.mod files.

steps:
 - uses: actions/checkout@v3
 - uses: actions/setup-go@v3
   with:
     go-version-file: 'path/to/go.mod'
 - run: go version

Besides, the following pull requests included in this release:

• Fix condition for GOPATH output #221
• Added go-version output #85
• Do not export GOROOT for Go versions >= 1.9 #175
• Update @zeit/ncc to @vercel/ncc #229

v3.0.0

What's Changed

• Update default runtime to node16 (#192)
• Update package-lock.json file version to 2 (#193) and @types/node to 16.11.25 (#194)
• Remove the stable input and fix SemVer notation (#195)

Breaking Changes

With the update to Node 16, all scripts will now be run with Node 16 rather than Node 12.

This new major release removes the stable input, so there is no need to specify additional input to use pre-release versions. This release also corrects the pre-release versions syntax to satisfy the SemVer notation (1.18.0-beta1 -> 1.18.0-beta.1, 1.18.0-rc1 -> 1.18.0-rc.1).

steps:
  - uses: actions/checkout@v2
  - uses: actions/setup-go@v3
    with:
      go-version: '1.18.0-rc.1' 
  - run: go version

Add check-latest input

In scope of this release we add the check-latest input. 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 from go-versions repository. By default check-latest is set to false.
Example of usage:

steps:
  - uses: actions/checkout@v2
  - uses: actions/setup-go@v2
    with:
      go-version: '1.16'
      check-latest: true
  - run: go version

Moreover, we updated @actions/core from 1.2.6 to 1.6.0

v2.1.5

In scope of this release we updated matchers.json to improve the problem matcher pattern. For more information please refer to this pull request

v2.1.4

What's Changed

• Fix extractor selection on windows by @paulcacheux in #141

New Contributors

• @paulcacheux made their first contribution in #141

Full Changelog: v2.1.3...v2.1.4

v2.1.3

• Updated communication with runner to use environment files rather then workflow commands

v1.1.3

• Updated communication with runner to use environment files rather then workflow commands

v2.1.2

This release includes vendored licenses for this action's npm dependencies.

v2.1.1

Switch to main branch of go-versions repository to consume latest added versions