-
Notifications
You must be signed in to change notification settings - Fork 1.4k
🌱 Bump Go 1.24 #12128
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 Go 1.24 #12128
Conversation
We should merge #12088 at first since the golangci-lint version that Go1.24 is available is only golangci-lint v2. |
/hold We usually use the same go version used by K8s version we are importing, and we import the same K8s version used by the controller runtime version we are using. |
Thanks! |
I would like to do the CR bump. I'm usually using CAPI as a final verification for CR before the CR release is published. I will coordinate with you that this PR is merged right before. Can you please rebase this PR? |
@sbueringer EDIT |
This failure is led by Go 1.24 since the go test run the vet implicitly before run test. Since 1.24, printf linter is called every time, then I disabled it on golanci.yml to deal with these issues on another PR. But it seems to deal with it too including with this PR. |
Okay, it works correctly 😄 |
We met the vulnerability, then I decide to upgrade from go1.24.0 to go1.24.2. |
/retest |
Thx! rebased. |
Thx! /lgtm Waiting with merge until we can be sure that we'll get a CR v0.21.0 release ahead of the CAPI alpha we want to do in a few weeks |
LGTM label has been added. Git tree hash: 6d2002d939e9353ec159a0f77321ec13626a72da
|
lgtm, besides google cloud build image bump |
bf0ae43
to
d1c4e1e
Compare
Signed-off-by: sivchari <[email protected]>
Last open point: update the cloudbuild yaml files to use |
cloudbuild.yaml
Outdated
@@ -5,7 +5,7 @@ options: | |||
substitution_option: ALLOW_LOOSE | |||
machineType: 'E2_HIGHCPU_8' | |||
steps: | |||
- name: 'gcr.io/k8s-staging-test-infra/gcb-docker-gcloud@sha256:4e830b673791d5595719bc6c4ca62dce3746b4e20d749e45004254bc6ef0a140' # v20250116-2a05ea7e3d | |||
- name: 'gcr.io/k8s-staging-test-infra/gcb-docker-gcloud@sha256:fe4041d57c711070436d3c5b7702534b7158f464e9772aa9e333a5e0e24fd854' # v20250513-9264efb079 |
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 cannot pull this image
docker pull gcr.io/k8s-staging-test-infra/gcb-docker-gcloud@sha256:fe4041d57c711070436d3c5b7702534b7158f464e9772aa9e333a5e0e24fd854
Error response from daemon: manifest for gcr.io/k8s-staging-test-infra/gcb-docker-gcloud@sha256:fe4041d57c711070436d3c5b7702534b7158f464e9772aa9e333a5e0e24fd854 not found: manifest unknown: Requested entity was not found.
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 think this sha works sha256:63840f133e0dfeea0af9ef391210da7fab9d2676172e2967fccab0cd6110c4e7
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.
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.
Thx! I fixed it.
Nice catch btw. I discussed this with Christian and Fabrizio. Given that we are going to merge the CR bump ahead of the next release anyway we would like to merge the current PR as soon as it's ready (last finding should be: #12128 (comment)) |
Signed-off-by: sivchari <[email protected]>
/hold cancel (double checked the gcb-docker-gcloud images, now all good) |
LGTM label has been added. Git tree hash: ba67208b2af6fd5eb5c6279aa2f6e8e00a4792f0
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Part of #11642
/area dependency