ci: windows arm build

[0xbrayo]

Important

Add Windows ARM64 build support to build.yml and release.yml workflows.

• Workflows:
  • Add Windows ARM64 build support in build.yml and release.yml.
  • Add platform entry windows-latest with --target aarch64-pc-windows-msvc argument for Windows ARM64.

^{This description was created by for ff526a9. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to ff526a9 in 1 minute and 16 seconds

More details

• Looked at 26 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 4 drafted comments based on config settings.

1. .github/workflows/build.yml:21

• Draft comment:
  Consider using a unique identifier (e.g. 'windows-arm64') for the ARM build entry to differentiate it from the standard Windows build.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 30% vs. threshold = 50%
  The current setup uses the same platform identifier 'windows-latest' twice, but differentiates the ARM build using the args parameter. While using a unique identifier might make the configuration more readable, the current setup is functionally correct since GitHub Actions matrices can handle this pattern. The args parameter already clearly identifies the ARM target.
  The current setup might actually be intentional to ensure both builds use the same Windows runner environment. A different identifier might imply a different runner type.
  While the suggestion might improve readability, it's not clearly incorrect or problematic as is, and the current approach might be deliberately chosen to ensure consistent runner environments.
  This comment should be deleted as it suggests a change that isn't clearly necessary or beneficial, and the current implementation is functionally correct.

2. .github/workflows/release.yml:22

• Draft comment:
  Consider using a unique identifier (e.g. 'windows-arm64') for the ARM build entry to avoid confusion with standard Windows builds.
• Reason this comment was not posted:
  Marked as duplicate.

3. .github/workflows/build.yml:21

• Draft comment:
  Consider adding an explicit identifier (e.g. an 'arch' field) in the matrix for Windows ARM64 to differentiate it from the default 'windows-latest' entry.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

4. .github/workflows/release.yml:21

• Draft comment:
  Consider differentiating the Windows ARM64 entry (e.g. by adding an 'arch' field) to clarify its purpose versus the default Windows build.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

Workflow ID: wflow_OwhaDZWI5YgC47KU

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.