Verify published binaries run before archiving in CI

[Copilot]

Add binary verification step to CI workflow

Understanding the issue:

• The CI workflow builds binaries for 6 OS/arch combinations (Linux amd64/arm64, Windows amd64/arm64, macOS amd64/arm64)
• After dotnet publish, binaries should be tested to ensure they run
• The application already supports --version option
• Need to add a verification step after publish but before archiving

Plan

• Explore CI workflow structure
• Verify --version option exists
• Add verification step to workflow after publish
• Handle OS-specific binary paths (stack vs stack.exe)
• Test the changes locally
• Refactor to use matrix executable property (per feedback)
• Fix Windows ARM64 runner to use windows-11-arm
• Commit changes

Changes Made

1. Added executable property to each matrix entry (stack for Linux/macOS, stack.exe for Windows)
2. Added single "Test binary" step that:
   • Uses chmod +x with || true to make binary executable (no-op on Windows)
   • Executes ${{ matrix.executable }} --version using the matrix property
3. Changed Windows ARM64 runner from windows-latest to windows-11-arm to fix x64/ARM64 architecture mismatch

This approach is cleaner and more maintainable than OS-specific conditional steps.

Original prompt

This application is built for a variety of operating systems and architectures. As part of the CI workflow the binary for the relevant os+arch is built using dotnet publish and then uploaded as an artifact.

I want to make sure that the binary will actually run properly after it is built.

Add a step to the relevant part of the CI workflow during publish to run the built binary. The application has a --version (e.g. stack --version) option that can be run to check the version of the application, this should be sufficient to assert that the built binary can be run successfully.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[geofflamrock]

@copilot Instead of detecting the os and running separate steps for Linux vs Windows, add the exe name to the matrix values above and use that with a single verification step.

[Copilot]

Done. Added executable property to the matrix (stack/stack.exe) and replaced the two conditional steps with a single step that uses ${{ matrix.executable }}. The chmod +x command includes || true so it won't fail on Windows. (bd2ab0d)

[geofflamrock]

@copilot the windows arm64 ci build is failing because it's running on windows-latest which is x64. Is there another runner image that can be used for this?

[Copilot]

Changed to windows-11-arm which is the GitHub Actions runner image for Windows ARM64. This will run the build on native ARM64 hardware instead of x64. (33403a8)