ci(release): drop the Intel Mac leg — macos-13 no longer schedules#2
Merged
Merged
Conversation
A workflow_dispatch dry run had x86_64-unknown-linux-{gnu,musl} and
aarch64-apple-darwin all finish successfully while x86_64-apple-darwin sat
queued for 12+ minutes waiting for a runner. Because publish declares
needs: build, a leg that never gets scheduled hangs the entire release
instead of failing it — so a real tag push would have hung the same way.
Notably the musl leg, flagged in the spec as the one most likely to fight
(extism/wasmtime under fat LTO), built without trouble. The risk was the
runner label, not the linker.
Intel Macs build from source; an aarch64 binary will not run there.
Claude-Session: https://claude.ai/code/session_01QUGuvDUj6gG5xQPiN3X2bG
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
1 participant
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.
The
workflow_dispatchdry run onmainsettled both open questions about the release workflow:x86_64-unknown-linux-gnux86_64-unknown-linux-muslaarch64-apple-darwinx86_64-apple-darwin(macos-13)Two things worth recording:
The musl leg was fine. The design spec flagged it as "the leg most likely to fight" — extism pulls wasmtime/cranelift and the release profile is
lto = "fat"withcodegen-units = 1. It built without trouble. The actual failure was runner availability, which had been noted only as a passing follow-up.A never-scheduled leg is worse than a failing one.
publishdeclaresneeds: build, so an unscheduled leg hangs the release indefinitely rather than failing it. A realv0.1.0tag push would have hung exactly the same way — which is the entire argument for having rehearsed withworkflow_dispatchfirst.So the Intel Mac leg is removed rather than left to hang. Intel Macs build from source; an
aarch64-apple-darwinbinary will not run there. The workflow comment and both docs record why, so a future reader doesn't "helpfully" add it back.Docs updated: README's target list now says three and points Intel users at building from source; CLAUDE.md's release description matches and notes the
needs: buildinteraction.https://claude.ai/code/session_01QUGuvDUj6gG5xQPiN3X2bG