Hey there @OKaluza
Pinged our team on this one and discovered that the latest run for the
Deploy workflow on the default branch was cancelled, which is why the badge is showing as failed.
However, as @brightran mentioned, there are some other threads that show evidence of similar behavior under different circumstances. While this particular thread has an answer, I want to make mention of some efforts going on internally, here.
There is refresh work happening that should help with erroneous
failing tags being added to successful runs. There is no ETA that I can provide on this effort, and it specifically wouldn’t solve the problem here, but it should make that inadvertent tagging no longer a problem, once completed.
Thanks so much for raising this!