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.

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

ci: update go version for govulncheck (backport #14175) #14177

Merged
merged 1 commit into from
May 8, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented May 8, 2024

Update the version of Go used for govulncheck to get the latest CVE fix present in Go v1.22.3.

Related: #14027

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
  • Reviewed the developer guide on Submitting a Pull Request
  • Pending release notes updated with breaking and/or notable changes for the next minor release.
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Integration tests have been added, if necessary.

This is an automatic backport of pull request #14175 done by [Mergify](https://mergify.com).

Update the version of Go used for govulncheck to get the latest CVE fix
present in Go v1.22.3.

Signed-off-by: Blaine Gardner <blaine.gardner@ibm.com>
(cherry picked from commit f21f3f5)
go-version: "1.22.2"
go-version: "1.22"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1.13 actually uses go v1.21 to build. We should probably cancel this backport and apply a special fix to specify go-version: "1.21" for release-1.13. Or we should additionally start building 1.13 using v1.22. Thoughts @travisn ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This govulncheck is already using 1.22, so this should just affect this single action. Otherwise, this will fail for all 1.13 PRs, right?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm... true. I guess let's merge this and can follow up with 1.21 later if we want

@BlaineEXE BlaineEXE merged commit b610064 into release-1.13 May 8, 2024
51 of 52 checks passed
@mergify mergify bot deleted the mergify/bp/release-1.13/pr-14175 branch May 8, 2024 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants