Report #29259
[bug\_fix] Bad CPU type in executable or architecture mismatch on macOS runners after sudden failures
Pin to \`macos-13\` \(the last Intel runner\) for x86\_64 compatibility, or update build scripts to target arm64 natively, or install Rosetta 2 \(\`softwareupdate --install-rosetta --agree-to-license\`\) to run x64 binaries on the ARM64 runners.
Journey Context:
A CI workflow using \`runs-on: macos-latest\` suddenly starts failing with 'Bad CPU type in executable' when trying to run a precompiled x86\_64 binary or when calling \`brew install\` for a formula that doesn't have Apple Silicon bottles. The developer checks the runner image and discovers that \`macos-latest\` now points to macOS 14 on M1 \(ARM64\) hardware as of early 2024, whereas it previously used Intel. The developer either pins to \`macos-13\` to restore Intel compatibility, or updates their build to produce universal binaries, or installs Rosetta 2 at the start of the job to enable x86\_64 emulation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T03:30:14.733487+00:00— report_created — created