Conversation
The macos-13 runner sat queued for two hours and forty-eight minutes without starting; the other three targets had long since built. GitHub has been shrinking its Intel macOS capacity and a repository may simply not get one. The only other way to publish for an Intel Mac is to cross-compile on Apple silicon, where the integration suite cannot run the binary it produced. Shipping something no machine has executed is the one thing this workflow exists to prevent, so the matrix is macOS on Apple silicon and Linux on both architectures, and an Intel Mac builds from source. It is told so directly. Hitting the installer on an Intel Mac now explains why there is no binary and prints the three commands that build one, instead of reporting a 404 and leaving. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
v0.5.1was tagged and withdrawn without ever being published. This is why, and what it changes.What happened
The release matrix added Intel macOS and ARM Linux. ARM Linux built in minutes.
macos-13sat queued for two hours and forty-eight minutes and never started — GitHub has been shrinking its Intel macOS capacity, and a repository may simply not be given one. The run was cancelled and the tag deleted; since the workflow publishes only after every build succeeds, nothing had been released, sov0.5.0stayed latest throughout. That is the pipeline doing what it was written to do.The choice
Cross-compiling for Intel on an Apple silicon runner would produce an archive, but the integration suite could not run the binary it produced, and neither could the verify job. Publishing a binary no machine has executed is the one thing this workflow exists to prevent.
So: macOS on Apple silicon, Linux on x86-64 and arm64. All three are built, tested against the file that ships, published as a prerelease, installed from that release on their own platform, checked to enforce there, and only then promoted.
An Intel Mac builds from source, and is told so by name — the installer explains why there is no binary and prints the three commands that build one, rather than reporting a 404 and leaving. Both READMEs say it too.
Why not just ship four and hope
Because that is the claim this project keeps making and would have broken: a restriction porta cannot enforce refuses the run; a platform porta cannot test does not get a binary.
🤖 Generated with Claude Code