Skip to content

Conversation

@arshadd-b
Copy link
Contributor

What this PR does / why we need it:
Bump Go version to 1.24.9
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 #

@k8s-ci-robot k8s-ci-robot added this to the v1.10 milestone Nov 4, 2025
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Nov 4, 2025
@k8s-ci-robot k8s-ci-robot added do-not-merge/needs-area PR is missing an area label size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 4, 2025
@wendy-ha18
Copy link
Member

I'm not sure if should we also bump kubernetes_version to v1.34.0 for CAPI v1.10:
https://github.com/kubernetes-sigs/cluster-api/blob/release-1.10/Tiltfile#L5

Kubernetes v1.34 also supported Go v1.24.9: https://github.com/kubernetes/kubernetes/blob/release-1.34/.go-version

@arshadd-b arshadd-b force-pushed the Bump-Go-Version branch 2 times, most recently from 703380c to 6b54787 Compare November 4, 2025 12:09
@chrischdi
Copy link
Member

/retitle [release-1.10] 🌱 Bump Go version to 1.24.9

@k8s-ci-robot k8s-ci-robot changed the title 🌱 Bump GoVersion to 1.24.9 [release-1.10] 🌱 Bump Go version to 1.24.9 Nov 4, 2025
with:
version: v1.63.4
args: --out-format=colored-line-number
version: v2.4.0
Copy link
Member

Choose a reason for hiding this comment

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

Maybe we can get around bumping to v2 via using v1.64.0 here.

Bumping to v2 involves way more than we probably want on this PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes checked it many changes are there if we move to v2
will try upgrading to v1.64.0

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think after upgrading it to 1.64.2 , have some errors , will fix those

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There are some issues with 1.64.2 in ginkgolinter
I see in 1.64.3 it is fixed https://golangci-lint.run/product/changelog/#1646

@chrischdi
Copy link
Member

We have to adapt #6356

I'm not sure if should we also bump kubernetes_version to v1.34.0 for CAPI v1.10: release-1.10/Tiltfile#L5

Kubernetes v1.34 also supported Go v1.24.9: kubernetes/kubernetes@release-1.34/.go-version

This is for release-1.10, so no we should not bump any kubernetes versions.

@arshadd-b arshadd-b force-pushed the Bump-Go-Version branch 2 times, most recently from 50ca7bf to 7b7ff11 Compare November 4, 2025 16:15
@wendy-ha18
Copy link
Member

another minor note but should we also update golangci-lint v1.64.2 in this file as well? (for CAPI release v1.10)

version: v1.63.4
name: golangci-lint-kal-v1.63.4

@arshadd-b arshadd-b force-pushed the Bump-Go-Version branch 5 times, most recently from a36c56a to 581e449 Compare November 5, 2025 13:51
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 5, 2025
@mboersma
Copy link
Contributor

mboersma commented Nov 6, 2025

Go v1.24.10 is out now, just FYI. See also #12962, which we can cherry-pick if you don't want to update this PR.

Copy link
Member

@chrischdi chrischdi left a comment

Choose a reason for hiding this comment

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

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 6, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: bc6c2d189606e1b3c0a6cd2dcad62cf6938c50aa

@sbueringer sbueringer added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Nov 7, 2025
@sbueringer
Copy link
Member

Thx everyone. Let's backport 1.24.10 on top

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 7, 2025
@sbueringer
Copy link
Member

/cherry-pick release-1.9

@k8s-infra-cherrypick-robot

@sbueringer: once the present PR merges, I will cherry-pick it on top of release-1.9 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.9

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.

@sbueringer
Copy link
Member

/area dependency

@k8s-ci-robot k8s-ci-robot added area/dependency Issues or PRs related to dependency changes and removed do-not-merge/needs-area PR is missing an area label labels Nov 7, 2025
@k8s-ci-robot k8s-ci-robot merged commit 941e4e2 into kubernetes-sigs:release-1.10 Nov 7, 2025
20 checks passed
@k8s-infra-cherrypick-robot

@sbueringer: #12945 failed to apply on top of branch "release-1.9":

Applying: Bump GoVersion to 1.24.9
Using index info to reconstruct a base tree...
M	Makefile
M	Tiltfile
M	go.mod
M	netlify.toml
Falling back to patching base and 3-way merge...
Auto-merging netlify.toml
Auto-merging go.mod
Auto-merging Tiltfile
Auto-merging Makefile
CONFLICT (content): Merge conflict in Makefile
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Bump GoVersion to 1.24.9

In response to this:

/cherry-pick release-1.9

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.

@sbueringer
Copy link
Member

Can you try to open the same PR for 1.9?
If it turns out to be too much work let's not do it though.
There are no further releases for 1.9 planned would be just nice to get the cve scan green

@arshadd-b
Copy link
Contributor Author

Can you try to open the same PR for 1.9? If it turns out to be too much work let's not do it though. There are no further releases for 1.9 planned would be just nice to get the cve scan green

sure will open a PR and see


go 1.23.0

godebug default=go1.23
Copy link
Member

Choose a reason for hiding this comment

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

Just noticed, we have more than this go.mod. This change should be in all go.mod files 🤔

Copy link
Member

Choose a reason for hiding this comment

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

Yup let's follow-up for that

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/dependency Issues or PRs related to dependency changes cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants