Repository navigation
Conversation
Add a windows_arm64 (aarch64-pc-windows-msvc) leg to the shared release pipeline, built natively on windows-11-arm so the verify gates can run the binary. Wire it into the asset-manifest and release-completeness checks and the release-notes table; both nightly and stable channels. install.ps1 now detects the OS architecture (registry, RuntimeInformation, env vars — robust to an x64 PowerShell under emulation), prefers windows_arm64 on ARM64, and falls back to windows_amd64 for releases that predate it. New -Platform override. Nightly install-smoke gains windows-11-arm, runs install.ps1 under both PowerShell 7 and Windows PowerShell 5.1, and asserts the installed q2.exe's PE machine type matches the runner. Plan: claude-notes/plans/2026-10-08-windows-arm64-nightly.md Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
cscheid
deleted the
feature/bd-windows-arm64-nightly-xms5p652-ship-native-windows-arm64
branch
October 8, 2026 19:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Braid:
bd-windows-arm64-nightly-xms5p652· Plan:claude-notes/plans/2026-10-08-windows-arm64-nightly.mdSomeone asked for Windows ARM binaries in the nightlies. Today ARM64 Windows gets
windows_amd64and runs it under x64 emulation.Changes
release-pipeline.yml: newwindows_arm64build leg (aarch64-pc-windows-msvc), built natively onwindows-11-arm. An x64 host can't execute an ARM64 binary, and the verify gates need to run it. This is the same reasoning aslinux_arm64onubuntu-24.04-arm.install.ps1:RuntimeInformation, then env vars. This holds up when an x64 PowerShell runs under emulation.windows_arm64and falls back towindows_amd64for releases that predate it.-Platformoverride.nightly.ymlinstall-smoke:windows-11-arm.q2.exe's PE machine type (0x8664/0xAA64) matches the runner, so the x64 fallback can't hide a missing ARM64 asset.Testing
actionlintpasses on all three workflows.install.ps1was exercised offline with pwsh 7.6 and a mocked GitHub API, covering all selection and fallback paths (details in the plan).force: true, publish: false): https://github.com/quarto-dev/q2/actions/runs/37824531935. This is the first build of the new leg. The PR isn't ready to merge until it's green.install-smokeonly runs against a published nightly, so the first scheduled nightly after merge is the first end-to-end check of the installer changes on real ARM hardware.🤖 Generated with Claude Code