Possible bug in your CI?

I happened to notice that tags 0.0.1 and 0.0.2 were recently modified on Quay.io, even though the most recently modified semver tag should be 1.0.2. It's possible someone specifically re-built the image/catalog/bundle against those git release tags, and no harm done, but wanted to make sure you were aware in case your CI is unexpectedly pushing the wrong tag on occasion. (0.0.2 also happens to match the manifest for the dev tag)

No file or test is named. Review the CI job responsible for pushing Quay.io images and compare its handling of tags 0.0.1, 0.0.2, 1.0.2, and dev; determine whether the older tags were intentionally rebuilt or incorrectly published, then verify the tagging behavior.

Written by the indexing model from the issue text.