Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update actions/setup-go action to v5 #314

Closed
wants to merge 2 commits into from
Closed

chore(deps): update actions/setup-go action to v5 #314

wants to merge 2 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 9, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
actions/setup-go action major v2.1.3 -> v5.0.0

Release Notes

actions/setup-go (actions/setup-go)

v5.0.0

Compare Source

What's Changed

In scope of this release, we change Nodejs runtime from node16 to node20 (https://github.com/actions/setup-go/pull/421). Moreover, we update some dependencies to the latest versions (https://github.com/actions/setup-go/pull/445).

Besides, this release contains such changes as:

New Contributors

Full Changelog: actions/setup-go@v4...v5.0.0

v4.1.0

Compare Source

What's Changed

In scope of this release, slow installation on Windows was fixed by @​dsame in https://github.com/actions/setup-go/pull/393 and OS version was added to primaryKey for Ubuntu runners to avoid conflicts (https://github.com/actions/setup-go/pull/383)

This release also includes the following changes:

New Contributors

Full Changelog: actions/setup-go@v4...v4.1.0

v4.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: actions/setup-go@v4...v4.0.1

v4.0.0

Compare Source

In scope of release we enable cache by default. The action won’t throw an error if the cache can’t be restored or saved. The action will throw a warning message but it won’t stop a build process. The cache can be disabled by specifying cache: false.

steps:
  - uses: actions/checkout@v3
  - uses: actions/setup-go@v4
    with:
      go-version: ‘1.19’
  - run: go run hello.go

Besides, we introduce such changes as

v3.5.0: Add support for stable and oldstable aliases

Compare Source

In scope of this release we introduce aliases for the go-version input. The stable alias instals the latest stable version of Go. The oldstable alias installs previous latest minor release (the stable is 1.19.x -> the oldstable is 1.18.x).

Stable
steps:
  - uses: actions/checkout@v3
  - uses: actions/setup-go@v3
    with:
      go-version: 'stable'
  - run: go run hello.go
OldStable
steps:
  - uses: actions/checkout@v3
  - uses: actions/setup-go@v3
    with:
      go-version: 'oldstable'
  - run: go run hello.go

v3.4.0: Add support for go.work and pass the token input through on GHES

Compare Source

In scope of this release we added support for go.work file to pass it in go-version-file input.

steps:
  - uses: actions/checkout@v3
  - uses: actions/setup-go@v3
    with:
      go-version-file: go.work
  - run: go run hello.go

Besides, we added support to pass the token input through on GHES.

v3.3.1: Fix cache issues and update dependencies

Compare Source

In scope of this release we fixed the issue with the correct generation of the cache key when the go-version-file input is set (https://github.com/actions/setup-go/pull/267). Moreover, we fixed an issue when the cache folder was not found. Besides, we updated actions/core to 1.10.0 version (https://github.com/actions/setup-go/pull/273).

v3.3.0: Support architecture input and fix Expand-Archive issue

Compare Source

This release introduces support for architecture input for setup-go action #​253. It also adds support for arm32 architecture for self-hosted runners. If architecture is not provided action will use default runner architecture.
Example of usage:

steps:
- uses: actions/checkout@v3
- uses: actions/setup-go@v3
  with:
   go-version: '1.16'
   architecture: arm

This release also provides fix for issue #​241. #​250 adds support for using explicit filename for Windows which is necessary to satisfy Expand-Archive's requirement on .zip extension.

v3.2.1: Update actions/cache version to 3.0.0

Compare Source

In scope of this release we updated actions/cache package as the new version contains fixes for caching error handling

v3.2.0: Support for caching dependency files and compiler's build outputs

Compare Source

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

v3.1.0: Add go-version-file input

Compare Source

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:

v3.0.0

Compare Source

What's Changed
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

v2.2.0: Add check-latest input

Compare Source

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

Compare Source

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

Compare Source

What's Changed

New Contributors

Full Changelog: actions/setup-go@v2.1.3...v2.1.4

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the renovate label Dec 9, 2023
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Dec 9, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

@glooms glooms closed this Feb 29, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Feb 29, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/actions-setup-go-5.x branch February 29, 2024 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
renovate
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@glooms