Images with Tags I.e. not the "latest" are updated frequently

[Nanoemc]

Some of the 0.7 images (I.e. coffea-base-almalinux8
) and coffea 2024 images (I.e. coffea-dask-almalinux8) have their package versions updated at the same frequency as the latest images. It causes issues with analysis pipelines and with the EAF, maybe there should be a latest-2024-py3.x tag and a latest-0.7.22-py3.x tag to avoid this in the future. It is hard to have a stable pipeline when some of the tagged images (not latest) are changing.

[nsmith-]

So, concretely, we do have what I would call a bug in the github action: when we bump a version of coffea-dask (i.e. coffea CalVer) we re-render also the coffea-base image, which may cause some unpinned versions to be updated and potentially break if the tests do not catch issues. For example, when #33 was merged the CI pushed a new image overwriting the tag coffea-base-almalinux8:0.7.22-py3.10: https://github.com/CoffeaTeam/af-images/actions/runs/11013386721/job/30581631518
We probably want all tags but latest to be permanent.

[nsmith-]

Perhaps we can open a new issue but there is more to discuss with respect to image version tags. For example, we may want to start a separate af-image versioning scheme rather than staying in lock-step with coffea.

[oshadura]

oh, I didnt want to close it, I just want to test how it looks like fixed version of workflow

[oshadura]

Now I think I have the workflow similar to what is doing dask:

• we generate repository tags (see https://github.com/CoffeaTeam/af-images/tags) each time there is a new version of coffea released and when tag is pushed we build only once the image 2024.9.1-py3.11 == permanent tag
• each time we merge something in the main branch we push the dev-py3.10 tag == not permanent
• probably latest, latest-pyxxx then could gone e.g. latest-py3.11

(all tags https://hub.docker.com/r/coffeateam/coffea-dask-almalinux9/tags)