feat: add multi-architecture release artifacts

[honnix]

Summary

• Add explicit GOOS/GOARCH cross-compilation to the release workflow
• Produce binaries for linux/amd64, linux/arm64, darwin/amd64, darwin/arm64, and windows/amd64
• Set CGO_ENABLED=0 and use explicit -o flag for consistent output naming
• Artifact names now include architecture (e.g. keep-sorted_linux_amd64 instead of keep-sorted_linux)

Motivation

The current workflow builds one binary per OS using the runner's native architecture. With GitHub Actions runners moving to arm64 for macOS, there's no darwin/amd64 binary for Intel Macs, and there has never been a linux/arm64 binary.

Breaking change

Artifact names change from keep-sorted_<os> to keep-sorted_<os>_<arch>. Users scripting downloads against the old names will need to update.

Test plan

• Verify the workflow YAML is valid
• Trigger a test release on the fork to confirm all 5 matrix jobs produce correctly named binaries
• Verify cross-compiled binaries with file command (ELF ARM aarch64, Mach-O x86_64, etc.)

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[honnix]

Artifact names change from keep-sorted_ to keep-sorted__. Users scripting downloads against the old names will need to update.

If this is critical I can try to keep the backward compatibility.

[honnix]

@JeffFaer Does this make sense? Thanks.

[JeffFaer]

Artifact names change from keep-sorted_<os> to keep-sorted_<os>_<arch>. Users scripting downloads against the old names will need to update.

No, that breaking change seems fine to me. I think this makes sense. Thank you for taking this on!

Are you planning on running through those testing steps yourself?

[honnix]

Are you planning on running through those testing steps yourself?

I think most of them could only be exercised via actions. I can probably test in my fork.

[honnix]

Are you planning on running through those testing steps yourself?

I think most of them could only be exercised via actions. I can probably test in my fork.

https://github.com/honnix/keep-sorted/releases/tag/test all look correct. I verified the binaries.

[honnix]

Wait a sec. Looks like removing the suffix is actually wrong. nvm

[honnix]

Thank you for merging this. Would you mind cutting a new release?

[honnix]

@JeffFaer A gentle ping. Thanks.