Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update x64/Arm Mac runners in GH Actions #155

Merged
merged 1 commit into from
Apr 30, 2024

Conversation

sergeichestakov
Copy link
Contributor

Why

I found out today that the macos-latest GH actions runner got switched out from under our feet in the past month since we last published and now the machine that runs those actions is an Apple Silicon (ARM) chip instead of an older Intel-based Mac. See relevant changelog: https://github.blog/changelog/2024-04-01-macos-14-sonoma-is-generally-available-and-the-latest-macos-runner-image/

The implication of this is that now both our "x64" and "arm64" jobs in GH actions are, in fact, producing arm64 based artifacts.

What changed

Update x64/Arm Mac runners in GH Actions. Now, the macos-latest runner corresponds to Apple Silicon (ARM) machines, meaning we no longer need the xlarge runner, and the macOS-12 runner corresponds to Intel chip builds.

Test plan

Should produce 2 separate DMGs, one for each architecture, on next run 🤞 In the meantime, the "runner details" in the GH actions logs in CI should indicate that they are running on the appropriate architecture.

@sergeichestakov sergeichestakov self-assigned this Apr 30, 2024
@sergeichestakov sergeichestakov requested review from a team, moudy, szymonkaliski and ink404 and removed request for a team April 30, 2024 20:04
@sergeichestakov sergeichestakov merged commit ac84bc4 into main Apr 30, 2024
9 checks passed
@sergeichestakov sergeichestakov deleted the @sergeichestakov/update-x64-mac-runner branch April 30, 2024 20:54
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.

2 participants