Iván Valdés Castillo

> #13980 as reference for previous work in this area. @serathius, I love the idea of having it automated after we push a tag (as I think we also discussed...

/assign As we're all aligned, I'll go ahead and draft a PoC PR.

Thanks for the initiative, @bavarianbidi. Although I think it'd be a good idea to use `goreleaser` for etcd, the build process (and script) is a bit more complex, as it...

> Thanks @ivanvc for the fast reply. > I totally understand your approach with small incremental steps. `goreleaser` is quite good in creating container images, binaries, ... in one step....

Hi @bavarianbidi, I'd suggest first to start by following up on https://github.com/etcd-io/etcd/issues/13980#issuecomment-1116360156 and https://github.com/etcd-io/etcd/issues/17873.

Setting the release as a prerelease or not the latest in a draft release does not seem to work as expected. I had success publishing the release using the CLI...

To do: - [x] Add a verification step to check uploaded contents (ref issue: #19270) - #19520 - [ ] Automate releasing draft release (it would be better after doing...

This will likely change whenever we're able to bring more automation to the release process.

> Are there still work left for the cobra-migration ? I think we can reuse the list from https://github.com/etcd-io/bbolt/issues/472#issuecomment-1674784719. But we may need to update it. I have a draft...

After a sweep of fixes merged in the main branch after 3.5.14, I found these two potential backports: * https://github.com/etcd-io/etcd/pull/18186 * https://github.com/etcd-io/etcd/pull/18108 Do we want to backport any of these?...