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

Bump CAPM3 1.7 release branch to Golang 1.22 #1828

Closed
tuminoid opened this issue Jul 3, 2024 · 5 comments
Closed

Bump CAPM3 1.7 release branch to Golang 1.22 #1828

tuminoid opened this issue Jul 3, 2024 · 5 comments
Assignees
Labels
triage/accepted Indicates an issue is ready to be actively worked on.
Milestone

Comments

@tuminoid
Copy link
Member

tuminoid commented Jul 3, 2024

Release branch release-1.7 has Golang 1.21.x in use. Golang 1.21 support ends in August 2024, when Golang 1.23 is released.

CAPM3 1.7 is in support for quite a while still, so we need to bump it to Go 1.22 before next patch release.

@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Jul 3, 2024
@tuminoid tuminoid added this to the CAPM3 - 1.7.2 milestone Jul 3, 2024
@Rozzii
Copy link
Member

Rozzii commented Jul 3, 2024

/triage accepted

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Jul 3, 2024
@NymanRobin
Copy link
Member

/assign

@NymanRobin
Copy link
Member

/close Done in #1852

@Rozzii
Copy link
Member

Rozzii commented Jul 26, 2024

/close

@metal3-io-bot
Copy link
Contributor

@Rozzii: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Status: Done / Closed
Development

No branches or pull requests

4 participants