GitHub Actions: Bump actions/setup-go from 3 to 4

dependabot[bot] commented 11 months ago

Release notes

Sourced from actions/setup-go's releases.

v4.0.0

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

Allow to use only GOCACHE for cache

Bump json5 from 2.2.1 to 2.2.3

Use proper version for primary key in cache

Always add Go bin to the PATH

Add step warning if go-version input is empty

Add support for stable and oldstable aliases

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
Add support for go.work and pass the token input through on GHES

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
</tr></table> 

... (truncated)

Commits

93397be Fix Install on Windows is very slow (#393)
27eec5b Merge pull request #396 from actions/dependabot/npm_and_yarn/semver-6.3.1
ecfc77a Merge pull request #397 from actions/dependabot/npm_and_yarn/word-wrap-1.2.4
1b80a11 Bump word-wrap from 1.2.3 to 1.2.4
b1c3434 Fix licensing for Semver 6.3.1
0bb97b1 Rebuild after updating Semver
4220624 Bump semver from 6.3.0 to 6.3.1
db8764c Bump tough-cookie and @azure/ms-rest-js (#392)
08b314a Merge pull request #383 from akv-platform/issue-368
4e0b6c7 Limit to Linux only
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

netlify[bot] commented 11 months ago

Deploy Preview deleted from internal cluster!

Name	Link
Latest commit	a659cd15a8434041ea2e898705f5806ed176b1dd
Deploy Preview	~https://odo-dev-pr-7124.odo-test-kubernete-449701-49529fc6e6a4a9fe7ebba9a3db5b55c4-0000.eu-de.containers.appdomain.cloud/~

openshift-ci[bot] commented 11 months ago

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.