-
Notifications
You must be signed in to change notification settings - Fork 9.9k
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
Update Go to 1.23.6/1.22.12 #19333
Comments
/assign |
This was referenced Feb 4, 2025
We also have bbolt |
Ah, thank you for pointing it out. I missed that new branch. |
All done. |
Thanks for the quick turnaround, @marcelfranca and @ArkaSaha30 🙇 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be added?
Golang 1.23.6 and 1.22.12 were released today. According to our Dependency management documentation, we want to stay on the latest patch version. This means updating the
release-3.4
andrelease-3.5
branches to 1.22.12 andmain
to 1.23.6.Completion tracking below:
main
: go v1.23.6 - Update golang toolchain to 1.23.6 #19335release-3.5
: go v1.22.12 - [3.5] Update golang toolchain to 1.22.12 #19336release-3.4
: go v1.22.12 - [3.4] Update golang toolchain to 1.22.12 #19337CHANGELOG
- changelog: update GO entry to reflect 1.22.12 update #19338main
: go v1.23.6 - update golang toolchain to 1.23.6 bbolt#891release-1.3
: v1.22.12 - [1.3] update golang toolchain to 1.22.12 bbolt#892release-1.4
: v1.23.6 - [1.4] backport: update golang toolchain to 1.23.6 bbolt#893main
: go v1.23.6 - Update golang toolchain to 1.23.6 raft#260release-3.6
: go v1.23.6 - [3.6] Update golang toolchain to 1.23.6 raft#261etcd-io/gofail
main
: go v1.22.12 - Updates golang toolchain to version 1.22.12 gofail#97etcd-io/auger
main
: go v1.23.6 - Update golang toolchain to version 1.23.6 auger#201etcd-io/etcd-operator
: go v1.23.6 - Update golang toolchain to version 1.23.6 etcd-operator#63Please look at the previous issues and their pull requests, e.g., #19210 and #19000.
Why is this needed?
To keep the project up to date with the latest Go versions. And to address CVE-2025-22866.
The text was updated successfully, but these errors were encountered: