[RFE] Auto-detect latest release versions in release builds

t-lo commented 7 months ago

Current situation

While new Kubernetes patch-level releases of all supported minor versions are auto-detected and the latest one is built, a similar feature is not implemented for docker, docker-compose, and wasmtime.

Impact

New versions need to be specified manually in order to be included in a release build.

Ideal future situation

New versions are automatically detected by release builds. Ideally, the implementation is modular and makes it easy to add new components / sysexts to the release auto-build.

Follow-up tasks

build new releases on a schedule (e.g. daily, weekly, etc) to keep "latest" release up to date with upstream releases.
~automatically tag "latest" in the build instead of relying on manual tagging.~ Done. Release CI action will re-tag.

jsalatiel commented 3 months ago

Could the same be added to cri-o ?

tormath1 commented 2 months ago

Most of the components are pulled from Github releases (except Tailscale, Docker and Keepalived). To get the latest we can inspire from how we fetch the CNI components for Kubernetes sysext: https://github.com/flatcar/sysext-bakery/blob/2112078b0804ac704d1bf9fa760d76f38f1270cf/create_kubernetes_sysext.sh#L92-L98

In this file we will set crio-latest for example: https://github.com/flatcar/sysext-bakery/blob/2112078b0804ac704d1bf9fa760d76f38f1270cf/release_build_versions.txt#L26 and we can still track specific versions.

For non github releases, it has to be handled with a custom way for each.

flatcar / sysext-bakery