projectcontour / contour-operator

Experimental repository to explore an operator for deploying Contour
Apache License 2.0
43 stars 34 forks source link

Bump actions/setup-go from 2 to 3 #563

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps actions/setup-go from 2 to 3.

Release notes

Sourced from actions/setup-go's releases.

Update actions/cache version to 3.0.0

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

v3.0.0

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

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

New Contributors

Full Changelog: https://github.com/actions/setup-go/compare/v2.1.3...v2.1.4

v2.1.3

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

... (truncated)

Commits
  • d0a58c1 Merge pull request #294 from JamesMGreene/patch-1
  • 3dcd9d6 Update to latest actions/publish-action
  • e983b65 Merge pull request #283 from koba1t/add_support_gowork_for_go-version-file
  • 27b43e1 Pass the token input through on GHES (#277)
  • 7678c83 add support gowork for go-version-file
  • c4a742c fix(): cache resolve version input (#267)
  • f556e5b Merge pull request #273 from rentziass/rentziass/update-actions-core
  • 514ae57 Update @​actions/core to 1.10.0
  • 30b9ddf Merge pull request #264 from e-korolevskii/258-not-throw-err-no-cache-folders
  • c4e1698 prettier format
  • Additional commits viewable in compare view


Dependabot compatibility score

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 will merge this PR once CI passes on it, as requested by @sunjayBhatia.


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 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)
sunjayBhatia commented 1 year ago

@dependabot squash and merge

codecov[bot] commented 1 year ago

Codecov Report

Base: 75.31% // Head: 75.54% // Increases project coverage by +0.22% :tada:

Coverage data is based on head (e599d6b) compared to base (48bf4df). Patch has no changes to coverable lines.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #563 +/- ## ========================================== + Coverage 75.31% 75.54% +0.22% ========================================== Files 29 29 Lines 2621 2621 ========================================== + Hits 1974 1980 +6 + Misses 507 504 -3 + Partials 140 137 -3 ``` | [Impacted Files](https://codecov.io/gh/projectcontour/contour-operator/pull/563?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=projectcontour) | Coverage Δ | | |---|---|---| | [internal/objects/service/service.go](https://codecov.io/gh/projectcontour/contour-operator/pull/563/diff?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=projectcontour#diff-aW50ZXJuYWwvb2JqZWN0cy9zZXJ2aWNlL3NlcnZpY2UuZ28=) | `83.84% <0.00%> (+1.15%)` | :arrow_up: | | [internal/controller/controller.go](https://codecov.io/gh/projectcontour/contour-operator/pull/563/diff?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=projectcontour#diff-aW50ZXJuYWwvY29udHJvbGxlci9jb250cm9sbGVyLmdv) | `74.66% <0.00%> (+2.00%)` | :arrow_up: | Help us with your feedback. Take ten seconds to tell us [how you rate us](https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=projectcontour). Have a feature suggestion? [Share it here.](https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=projectcontour)

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.