Release race condition in Konflux

We are facing release issue since a while now e.g: fedora-bootc-rawhide-standard have not been updated since January 12th.
So I took a closer look on what is going on.
AIUI we are facing release race conditions, below a timeline:

  1. a new commit is merged to the main branch, triggering the per-component on-push pipelines
  2. once built, Konflux creates a new snapshot for each build e.g: fedora-bootc-43-1, fedora-bootc-43-2, fedora-bootc-43-3. Each snapshot contains its updated component + the latest ones of the other components.
  3. Konflux runs the ITS against each snapshot. Let's say fedora-bootc-43-3 finishes first, the updated component of this snapshot e.g: fedora-bootc-43-minimal is then released, hence a new image of fedora-bootc-43-minimal in Quay. Then fedora-bootc-43-1 finishes, but as it's older than fedora-bootc-43-3 Konflux does not release it. e.g:
oc get snapshots  fedora-bootc-43-m7m2t  -o yaml
[...]
  - lastTransitionTime: "2026-01-28T12:54:52Z"
    message: Released in newer Snapshot
    reason: AutoReleased
    status: "True"
    type: AutoReleased

To have all the snapshots released, we'd need to have the exact same order between the build (snapshot created) and the ITS (snaphot validated) phases.
e.g: build-1 -> build-2 -> build-1-validated -> build-2-validated
Note: retriggering a failed ITS does not help, because Konflux reuses the same Snapshot which might be older than another one from the same commit.

As the integration tests of -minimal and -minimal-plus are faster than the -standard and -iot ones. The snapshots of those components are, most of the time if not ITS errors, validated and released first, making the others skipped.

I double checked our config, I think setting singleComponentMode to False would fix the issue, as Konflux would release all the components of the Snapshot.

05/02/26 update:

Edited by Joel Capitao