Skip to content

ci: run macOS Intel as a separate non-blocking job#163

Merged
JohannesHoppe merged 1 commit into
mainfrom
ci/intel-nonblocking
Jul 21, 2026
Merged

ci: run macOS Intel as a separate non-blocking job#163
JohannesHoppe merged 1 commit into
mainfrom
ci/intel-nonblocking

Conversation

@JohannesHoppe

Copy link
Copy Markdown
Member

Moves macos-13 (macOS x64 / Intel) out of the build matrix into its own continue-on-error job that publish does not depend on, so a tag-triggered release no longer waits on GitHub's retired/queued Intel runners. The four required-check platforms (Linux x64/arm64, macOS arm64, Windows x64) stay hard. Needed to publish v5.0.0.

Move macos-13 (macOS x64 / Intel) out of the build matrix into its own
continue-on-error job that the publish job does not depend on. GitHub's
Intel runners are being retired and routinely sit queued; a release must
not wait on runner availability, and continue-on-error alone does not help
because needs: build still waits for a queued job to reach a terminal state.

The four remaining build jobs stay hard (they are the branch-protection
required checks for main); only the non-required Intel job is soft.
@JohannesHoppe
JohannesHoppe merged commit 39e29fa into main Jul 21, 2026
16 of 18 checks passed
@JohannesHoppe
JohannesHoppe deleted the ci/intel-nonblocking branch July 21, 2026 19:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant