Previously, when a serial group start job was superseded by a higher-priority run in the same serial group, it was marked as failed — even though there was no issue and no action was needed. This caused the workflow to also show as failed, which could be misleading.
Now, superseded serial group start jobs are marked as not run instead. As a result, the workflow will show as skipped rather than failed, making it clear that the workflow was simply superseded — not broken.