Skip to content

build(ci): drop macos-15-intel from the test matrix#39

Merged
packetThrower merged 1 commit into
mainfrom
ci/drop-macos-15-intel
May 24, 2026
Merged

build(ci): drop macos-15-intel from the test matrix#39
packetThrower merged 1 commit into
mainfrom
ci/drop-macos-15-intel

Conversation

@packetThrower
Copy link
Copy Markdown
Owner

Summary

  • Removes the macos-15-intel matrix entry from ci.yml.
  • Updates the inline matrix comment to link the decision back to e3a4d28 (release.yml's earlier switch to cross-compiling x86_64 macOS from macos-26).

Why

release.yml stopped producing native x86_64 macOS binaries in e3a4d28 — cargo-packager's create-dmg step bombed on the macos-15-intel image with no recoverable diagnostic, and the fix was cross-compiling x86_64 macOS from macos-26 alongside the native arm64 build. CI was never updated to match: it kept testing natively on macos-15-intel while release shipped the cross-compiled output.

That's the worst of both worlds — we test one path and ship another with no overlap. The native-x86_64 CI run only verifies "the code that would have been built natively works," not "the cross-compiled output we actually distribute works."

This commit takes the consistent stance: both CI and release are Apple-Silicon-only on macOS.

Why this is a separate PR

This commit was originally part of #38's audit branch but landed on the branch ~32 minutes after #38 was merged, so the squash-merge didn't pick it up. Cherry-picked clean onto a fresh branch off main to avoid the 28-commit re-PR confusion that'd result from re-opening from the original branch (whose history no longer shares ancestry with main's squashed equivalent).

Test plan

  • actionlint clean on the workflow change
  • CI matrix on this PR has 5 entries instead of 6 (no macos-15-intel), all green

Risk

Low. No x86_64-specific code in the tree (no SIMD, no arch-gated cfg, no x86-only deps that aren't well-tested upstream).

🤖 Generated with Claude Code

release.yml stopped producing native x86_64 macOS binaries in
e3a4d28 — cargo-packager's create-dmg step bombed on the
macos-15-intel image with no recoverable diagnostic, and the
fix was cross-compiling x86_64 macOS from macos-26 alongside
the native arm64 build. CI was never updated to match: it kept
testing natively on macos-15-intel while release shipped the
cross-compiled output.

That's the worst of both worlds — we test one path and ship
another with no overlap. The native-x86_64 CI run only verifies
"the code that would have been built natively works," not "the
cross-compiled output we actually distribute works."

This commit takes the consistent stance: both CI and release
are Apple-Silicon-only on macOS. Drops the macos-15-intel
matrix entry, updates the inline comment to link the decision
back to e3a4d28's release-side rationale, and notes the path
back if native Intel builds ever return (unlikely given Apple's
transition timeline and GitHub's macos-15-intel sunset
schedule).

Saves ~5–7 min per CI run on a path that wasn't providing
shipping confidence anyway. No x86_64-specific code in the
tree (no SIMD, no arch-gated cfg, no x86-only deps that aren't
well-tested upstream) so the loss of native-x86 coverage is
low-risk.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@packetThrower packetThrower merged commit 90b3e6f into main May 24, 2026
6 checks passed
@packetThrower packetThrower deleted the ci/drop-macos-15-intel branch May 24, 2026 21:04
packetThrower added a commit that referenced this pull request May 24, 2026
Moves the DXGI probe entry from [Unreleased] into a versioned
[0.13.0] section dated today (the day all four PRs landed on
main: #38 audit + probe, #39 macos-15-intel drop, #36 gpui bump
that subsumed #37 gpui_platform bump). Adds a [Changed] entry
for the gpui upstream-rev bump.

Per CONTRIBUTING.md, dev-tool / internal-refactor changes stay
out of CHANGELOG — the file splits, cargo-deny, workflow_dispatch,
fmt + scripts CI gates, Tauri-residue deletion all land in the
audit but don't surface to users beyond "things compile + run as
before." git log carries the per-commit detail for anyone
spelunking; the CHANGELOG entry is what shows up in the GitHub
Release body.

The release date is set to today (2026-05-24) since that's when
the v0.13.0 content was finalized on main. If the stable tag
lands days after the beta, the date can be bumped — but since
all content is already merged, today is the accurate "this is
what the release contains" anchor.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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