Skip to content

Conversation

@k8s-infra-cherrypick-robot

This is an automated cherry-pick of #11377

/assign akhilerm

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
https://go.dev/doc/go1.24

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
@k8s-ci-robot
Copy link

Hi @k8s-infra-cherrypick-robot. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@dosubot dosubot bot added area/toolchain Build and Release Toolchain area/github_actions Pull requests that update GitHub Actions code go Pull requests that update Go code labels Feb 18, 2025
@akhilerm
Copy link
Member

/ok-to-test

name: Release

env:
GO_VERSION: "1.23.5"
Copy link
Member

Choose a reason for hiding this comment

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

I think we should use 1.23.6 instead of latest version for support release.

Copy link
Member

Choose a reason for hiding this comment

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

Yes. 💯 I think this was a miss when we made 2.0 branch cut. In other release branches we stick to the older stable of golang for making the release.

@akhilerm
Copy link
Member

/hold
We should not be using the latest golang for releases . #11401 (comment).

@akhilerm
Copy link
Member

akhilerm commented Feb 19, 2025

@fuweid Shouldnt we remove this also https://github.com/containerd/containerd/blob/main/core/mount/mount_idmapped_utils_linux_go122.go#L1, since we are not building on 1.22 anymore?

@fuweid
Copy link
Member

fuweid commented Feb 19, 2025

@fuweid Shouldnt we remove this also https://github.com/containerd/containerd/blob/main/core/mount/mount_idmapped_utils_linux_go122.go#L1, since we are not building on 1.22 anymore?

We can remove that file as long as we update this line to go1.23.

go 1.22.0

@akhilerm
Copy link
Member

Succeeded by #11410

@akhilerm akhilerm closed this Feb 19, 2025
@akhilerm
Copy link
Member

@fuweid Shouldnt we remove this also https://github.com/containerd/containerd/blob/main/core/mount/mount_idmapped_utils_linux_go122.go#L1, since we are not building on 1.22 anymore?

We can remove that file as long as we update this line to go1.23.

go 1.22.0

Its better to not remove it at this point then. Because we dont want to change the minimum version needed to build containerd immediately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/github_actions Pull requests that update GitHub Actions code area/toolchain Build and Release Toolchain do-not-merge/work-in-progress go Pull requests that update Go code ok-to-test size/S

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

6 participants