Image Releases are partially failing on `main`

[agilgur5]

Pre-requisites

• [X] I have double-checked my configuration
• [X] I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
• [X] I have searched existing issues and could not find a match for this bug
• [ ] I'd like to contribute the fix myself (see contributing guide)

What happened? What did you expect to happen?

The Windows build has been failing on CI since https://github.com/argoproj/argo-workflows/pull/13145.

While the Windows build is not used often, this means that the combined, multi-arch manifest for latest is not released either, per https://github.com/argoproj/argo-workflows/issues/13556#issuecomment-2331780589. This means that latest is outdated, and the arch-specific tags like latest-linux-amd64 need to be used instead for an up-to-date image

Version(s)

main, does not affect existing versions (yet)

Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.

n/a

Logs from the workflow controller

n/a

Logs from in your workflow's wait container

n/a

[agilgur5]

@Joibel could you look into this since it seems to be caused by #13145?