Stop blacklisting Go 1.22+, drop Go < 1.21 support, use Go 1.22 in CI#4292
Stop blacklisting Go 1.22+, drop Go < 1.21 support, use Go 1.22 in CI#4292AkihiroSuda merged 7 commits intoopencontainers:mainfrom
Conversation
c20f7e5 to
6b132ac
Compare
|
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? |
| ## 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.
Maybe add some note about Go 1.22
There was a problem hiding this comment.
I had this originally but got it removed as explained above: #4292 (comment) (TL;DR: the error message is explanatory enough).
|
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
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 <[email protected]>
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 <[email protected]>
Signed-off-by: Kir Kolyshkin <[email protected]>
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 <[email protected]>
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 <[email protected]>
As we're no longer supporting Go < 1.21. Signed-off-by: Kir Kolyshkin <[email protected]>
As we no longer support Go < 1.21. Signed-off-by: Kir Kolyshkin <[email protected]>
|
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.