Skip to content

Bump Go to 1.24.3 / 1.23.9 #19866

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

Open
14 of 20 tasks
Tracked by #19802
ivanvc opened this issue May 6, 2025 · 10 comments
Open
14 of 20 tasks
Tracked by #19802

Bump Go to 1.24.3 / 1.23.9 #19866

ivanvc opened this issue May 6, 2025 · 10 comments
Assignees
Labels
area/security priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. type/feature

Comments

@ivanvc
Copy link
Member

ivanvc commented May 6, 2025

What would you like to be added?

Golang 1.24.3 and 1.23.9 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, release-3.5, and release-3.6 branches to 1.23.9 and main to 1.24.3.

This patch includes the security fix for CVE-2025-22873.

Progress track:

Please look at the previous issues and their pull requests, e.g., #19713 and #19524.

Why is this needed?

To keep the project up to date with the latest Go versions. And to address CVE-2025-22873.

@ivanvc ivanvc added area/security type/feature priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels May 6, 2025
@ivanvc
Copy link
Member Author

ivanvc commented May 6, 2025

I'll work on etcd/release-3.6, as we want this for v3.6.0-rc.5.

/assign

ivanvc added a commit to ivanvc/etcd that referenced this issue May 6, 2025
Part of etcd-io#19866.

Signed-off-by: Ivan Valdes <[email protected]>
@Elbehery
Copy link
Member

Elbehery commented May 6, 2025

@ivanvc I can also help out

@ivanvc
Copy link
Member Author

ivanvc commented May 6, 2025

Sounds good. Do you want to work on the rest? Or a subset?

/assign @Elbehery

@Elbehery
Copy link
Member

Elbehery commented May 6, 2025

Sounds good. Do you want to work on the rest? Or a subset?

/assign @Elbehery

anything, as you decide Amigo :D :D

@ivanvc
Copy link
Member Author

ivanvc commented May 6, 2025

@Elbehery, feel free to work on the rest of the items, then.

@ivanvc
Copy link
Member Author

ivanvc commented May 9, 2025

@Elbehery, we're missing etcd's main branch. Would you be able to help with that?

Edit: And also the CHANGELOG entries for 3.4 and 3.5.

@Elbehery
Copy link
Member

@Elbehery, we're missing etcd's main branch. Would you be able to help with that?

Edit: And also the CHANGELOG entries for 3.4 and 3.5.

sure, I thought you would take the main branch :)

@Elbehery
Copy link
Member

done 👍🏽

@ivanvc
Copy link
Member Author

ivanvc commented May 11, 2025

I suggest not splitting the CHANGELOG pull requests into several and instead doing it in a single PR, as we've always done it.

Note: I needed to do release-3.6's because we were releasing the following day and wanted the CHANGELOG to be accurate.

@Elbehery
Copy link
Member

I suggest not splitting the CHANGELOG pull requests into several and instead doing it in a single PR, as we've always done it.

Note: I needed to do release-3.6's because we were releasing the following day and wanted the CHANGELOG to be accurate.

sorry I should have done it on one PR

one has been already merged, next time will notice this 👍🏽

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/security priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. type/feature
Development

No branches or pull requests

2 participants