Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 15 Packages Wiki Activity Actions

wai and wai-quantum releases: the x86_64 macOS legs on the Intel Mac #536

Merged
dcharlot merged 1 commit from ci/macos-x86_64-on-intel into main 2026-10-29 12:24:34 -04:00
Conversation 0 Commits 1 Files changed 2 +14 -8
dcharlot commented 2026-10-29 12:20:05 -04:00
Owner
Copy link

The macOS x86_64 legs of the two release workflows move to the Intel Mac (the iMac Pro, runner tx-imac-pro-macos, label macos-x86_64). The aarch64 legs stay on macos.

Why. Both legs were cross-built on the Apple-silicon runner. There, the checks that run what was built are skipped, because they run only when the triple is the host's:

  • wai-release.yml: the archive's own wai (hello, verify, dev --check).
  • wai-quantum-py-release.yml: the wheel's smoke test on Python 3.9.

So the x86_64 archive and wheel have been attached without ever being run. On the Intel Mac both run natively.

Change. Each macos job's matrix becomes an include that names its runner (runs-on: ${{ matrix.runner }}), the form wai-quantum-py-release.yml's Linux job already uses. max-parallel: 1 goes, since the two legs now run on different hosts.

Checked on the iMac before this PR:

  • The wai-v0.4.0 leg, run by hand: the archive builds natively, and its wai passes hello, verify and dev --check (7 of 7).
  • The released, cross-built wai-0.4.0-x86_64-apple-darwin.tar.gz: its SHA-256 matches, and it passes the same three, natively. The first time it has been run.
  • The runner is registered and polling. It is the official v12.12.0 source, built for darwin/amd64 because no Intel macOS build is published.
  • YAML parses (ruby); check-workflow-concurrency.sh passes; wfsteps.py reports no problem.

Both workflows run only on their tags, so this PR's own CI does not exercise them. The next wai-v* and wai-quantum-cli-v* tags will.

🤖 Generated with Claude Code

The macOS x86_64 legs of the two release workflows move to the Intel Mac (the iMac Pro, runner `tx-imac-pro-macos`, label `macos-x86_64`). The aarch64 legs stay on `macos`. **Why.** Both legs were cross-built on the Apple-silicon runner. There, the checks that run what was built are skipped, because they run only when the triple is the host's: - **`wai-release.yml`**: the archive's own `wai` (`hello`, `verify`, `dev --check`). - **`wai-quantum-py-release.yml`**: the wheel's smoke test on Python 3.9. So the x86_64 archive and wheel have been attached without ever being run. On the Intel Mac both run natively. **Change.** Each `macos` job's matrix becomes an `include` that names its runner (`runs-on: ${{ matrix.runner }}`), the form `wai-quantum-py-release.yml`'s Linux job already uses. `max-parallel: 1` goes, since the two legs now run on different hosts. **Checked on the iMac before this PR:** - The `wai-v0.4.0` leg, run by hand: the archive builds natively, and its `wai` passes `hello`, `verify` and `dev --check` (7 of 7). - The released, cross-built `wai-0.4.0-x86_64-apple-darwin.tar.gz`: its SHA-256 matches, and it passes the same three, natively. The first time it has been run. - The runner is registered and polling. It is the official v12.12.0 source, built for darwin/amd64 because no Intel macOS build is published. - YAML parses (ruby); `check-workflow-concurrency.sh` passes; `wfsteps.py` reports no problem. Both workflows run only on their tags, so this PR's own CI does not exercise them. The next `wai-v*` and `wai-quantum-cli-v*` tags will. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
wai and wai-quantum release workflows: the x86_64 macOS legs on the Intel Mac (macos-x86_64)
All checks were successful
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 8s
Details
standards workspaces build + test / macOS energy backends (pull_request) Has been skipped
Details
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 2m40s
Details
a546ffa1e3 
Each macOS leg runs on a Mac of its own architecture. The x86_64 one was cross-built on the
Apple-silicon runner, where the step that runs the archive's own wai (hello, verify,
dev --check) and the wheel's smoke test on Python 3.9 are skipped, since they run only when
the triple is the host's: the x86_64 archive and wheel were attached without ever being run.
On the Intel Mac (the iMac Pro, label macos-x86_64) both run natively. The two legs are on
different hosts now, so max-parallel: 1 is gone.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Transaction-Science/open-standards!536
No description provided.