ci: drop Intel macOS from release builds - #688
Merged
Merged
Conversation
macos-15-intel fails in Setup macOS (openssl@3: no bottle available) before cargo runs. Remove x86_64-apple-darwin from the release and hotfix build matrices, and have the install script tell Intel Mac users to use Apple Silicon, Linux, or compile locally.
n13
force-pushed
the
n13/drop-mac-x86-release
branch
from
September 1, 2026 03:11
037f784 to
f5befbb
Compare
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.11.0-rocket-fuel died in Setup macOS on
macos-15-intel(openssl@3: no bottle available) before cargo ran, which cancelled the other platforms. Intel Mac is no longer worth carrying as a release target.x86_64-apple-darwin/macos-15-intelfrom the Release Tag & Publish and hotfix build matrices.install-quantus-node.shtells Intel Mac users to use Apple Silicon, Linux, or compile locally, instead of downloading an asset that will not exist.No other workflow changes. After merge, rocket-fuel is re-fired the same way v0.8.0 was: delete the tag, re-merge the release-proposal PR.