In RHIDP-7906, we updated tagRelease.sh to push BOTH a 1.6.z and 1.6 tag to the rhdh repo (so that rhdh-local users can follow the https://quay.io/rhdh-community/rhdh:1.6 tag). This triggered two multi arch builds:

However the 1.6 tag used the commit SHA d1d310c2 whereas the 1.6.2 tag used 7cfe62b9:

Since nothing important changed between those commits in terms of the container image contents, this is fine.

But it would be better if the 1.6 tag used the same digest as the 1.6.z tag, for consistency.

This might be a "Github feature" or it might be a "tagRelease.sh bug"