windows not working properly

[caarlos0]

so, couple of issues:

• we can't use windows images on linux, not even pull them
• caching on windows and restoring on linux was broken
• artifacts.json need to have the paths on unix format (forward slashes) goreleaser/goreleaser@af38a4c

[caarlos0]

https://github.com/caarlos0/goreleaser-pro-split-merge-example-real/releases/tag/v0.0.2

except for the windows docker images, everything else is done

[douglascamata]

@caarlos0 the only way that I see this working with Windows container images is having a way to configure the continue command to skip certain OSes. Something like this:

1. Run the split builds.
2. Run a continue --merge --partial=darwin,linux command from a Linux node.
3. Run a continue --merge --partial=windows command from a Windows node.
4. Run a continue --merge --finalize.

The --partial option is an idea to indicate that it should continue merging/signing/SBOMing artifacts, built images, source archives, checksums, etc into the release based on the GOOS entry for it. The last command, with --finalize, indicates we are done preparing the release and goreleaser should proceed with running publishers and announcers.

Today I tried to set things up to run continue --merge from two different Github Workflows, one running on Windows with only Windows ./dist and the other with the Linux and macOS files.

The issue is that one of the two will produce a checksum artifact and uploaded it, then the other will try to do the same and fail because the artifact is already there. There might be other issues that happen further down the release processing, but I didn't get to see them. You can see the logs of my attempt here: https://github.com/douglascamata/opentelemetry-collector-releases/actions/runs/13771176732/job/38511232588

The solution that I propose should be able to handle this, because common release tasks should only be executed when we are finalizing the release.

[douglascamata]

Aaah, seem to have been able to achieve what I wanted today by adding replace_existing_artifacts: true to my release configuration. Even though it's not ideal, because it's doing more API calls than necessary, it seems to work. 😄