Automate quay.io contrib image tags on new releases? / Missing stable tags

[mchubby]

Hello,
According to https://github.com/containers/buildah/blob/main/contrib/buildahimage/README.md there are several distinct target images built and pushed on quay.io

Same question as #3365

at https://github.com/containers/buildah/releases there have been several stable releases (esp. ones with security fixes) but some or them do not have corresponding tags in quay.

Is it a manual approval process?

I have looked at the scheduled job https://github.com/containers/buildah/actions/workflows/multi-arch-build.yaml and there is no mention of a hardcoded version number.

Edit

So it is not 100% clear but this text

Built daily using the same Dockerfile as above. The buildah version will remain the "latest" available in Fedora

means

https://github.com/containers/buildah/blob/main/contrib/buildahimage/stable/Dockerfile is processed, the image will use "registry.fedoraproject.org/fedora:latest" as a source image

and yum install buildah, which means whatever has been packaged for that distribution version

so

podman run --it --rm registry.fedoraproject.org/fedora:latest /bin/bash

# dnf info buildah
Fedora 35 x86_64 (....) 
Version     : 1.23.3
Source      : buildah-1.23.3-2.fc35.src.rpm

which is the latest available tag for that "stable" image build on quay.
QED

https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2VWH6X6HOFPO6HTESF42HIJZEPXSWVIO/ security fixes properly applied.