-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Stop blacklisting Go 1.22+, drop Go < 1.21 support, use Go 1.22 in CI #4292
Conversation
c20f7e5
to
6b132ac
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
It took me a while to test locally that the go version dance was fine, but it indeed seem fine :)
btw, it seems the ubuntu builds are stalled.
We'll probably need to port the first 3 patches to release-1.1 (so that it will work with Go 1.22). |
This PR drops go 1.20.x tests, but they are marked as required in repo config -- this is why they are shown as "Expected -- waiting ...". I will fix the repo config accordingly (rm go 1.20.x, require go 1.22.x) once this PR will be ready to be merged (I guess once Go 1.21.4 is out). |
@opencontainers/runc-maintainers wdyt? |
@@ -27,7 +27,7 @@ A third party security audit was performed by Cure53, you can see the full repor | |||
|
|||
## Building | |||
|
|||
`runc` only supports Linux. It must be built with Go version 1.19 or higher. | |||
`runc` only supports Linux. It must be built with Go version 1.21 or higher. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add some note about Go 1.22
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had this originally but got it removed as explained above: #4292 (comment) (TL;DR: the error message is explanatory enough).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, one minor (optional) nit. Very optional, as that code will cease to exist in a few months :)
CentOS tests seem failing |
For CentOS stream 8, that may be expected; it's EOL since May 31 (just got hit by that in some CI pipeline that als had it in the Matrix) |
I guess we now have to replace CentOS with Alma, Rocky, or Oracle Linux? |
This one should be merged after go 1.22.4 has released. |
b72e13a
to
1600312
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Go 1.23 includes a fix (https://go.dev/cl/587919) so go1.23.x can be used. This fix is also backported to 1.22.4, so go1.22.x can also be used (when x >= 4). Finally, for glibc >= 2.32 it doesn't really matter. Add a note about Go 1.22.x > 1.22.4 to README as well. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Now when Go 1.22.4 is out it should no longer be a problem. Leave Go 1.21 for CentOS testing (CentOS 7 and 8 have older glibc) and Dockerfile (Debian 11 have older glibc). Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Go 1.20 was released in February 2023 and is no longer supported since February 2024. Time to move on. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
It is not needed since Go 1.20 (which was released in February 2023 and is no longer supported since February 2024). Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
As we're no longer supporting Go < 1.21. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
As we no longer support Go < 1.21. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Assuming that by the time 1.2.0 is out, everyone will use Go 1.22.x >= 1.22.4, I just dropped the restriction (and added a note to README). I think this is ready to be merged. WDYT @cyphar? |
High level overview:
See individual commits for details.