-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Plan to release etcd v3.5.18 #19119
Comments
I'd like to be a release advisor/shadow, as I'd like to see someone else running the release script after the first improvements from #18604. However, I can also be the lead if there are no volunteers. |
I haven't had much time in the last few weeks to help with etcd development but I think I could once again be a shadow for the release. I think I'm not yet familiar enough with the process to be a lead. |
@ivanvc would it be possible to include patches to |
Yeah, but it needs to be backported into the release-3.5 branch to get into the 3.5.x release as far as I understand: |
oof, of course you're correct, sorry, still seems i have holiday-brain. It would certainly be good to have those fixes included for us |
This makes sense. We're not directly affected by the vulnerability (https://github.com/etcd-io/etcd/actions/runs/12551556226/job/34996167337), but it's still a dependency with a CVE, and according to our Dependency Management documentation. |
@jmhbnz, would you be interested in being part of the release team? |
What would you like to be added?
The etcd patch release criteria has been met for our
release-3.5
stable release branch so we should releasev3.5.18
.The list of commits included since the previous release is: v3.5.17...release-3.5:
Work in progress CHANGELOG is: https://github.com/etcd-io/etcd/blob/main/CHANGELOG/CHANGELOG-3.5.md#v3518-tbc
List of pull requests we still need to backport from
main
torelease-3.5
before the patch release is issued:Release team
Why is this needed?
Regular patch releases are vital to ensure our users have bug-free and secure software.
The text was updated successfully, but these errors were encountered: