Skip to content

feat: Add macOS 14 ARM 64 runners to the matrix - #2132

Closed
Mr-Sunglasses wants to merge 1 commit into
pypa:mainfrom
Mr-Sunglasses:fix/2079
Closed

Mr-Sunglasses wants to merge 1 commit into
pypa:mainfrom
Mr-Sunglasses:fix/2079

Conversation

@Mr-Sunglasses

Copy link
Copy Markdown
Contributor

fix: #2079

Contributor checklist
  • Included tests for the changes.
  • PR title is short, clear, and ready to be included in the user-facing changelog.
Maintainer checklist
  • Verified one of these labels is present: backwards incompatible, feature, enhancement, deprecation, bug, dependency, docs or skip-changelog as they determine changelog listing.
  • Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

@webknjaz webknjaz left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rebase this once #2145 is in.

@webknjaz webknjaz left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI macos-latest already runs arm64. So the current patch doesn't change the runtime.
The idea of #2079 is to have both arm64 and intel jobs in CI.

Although, we have to be mindful of the CI resources as this would be computationally expensive. We need to be strategic about this and perhaps have two variants on cron and on merge rather than in PRs, for example.

This needs more research to be implemented correctly.

@webknjaz

webknjaz commented Jul 9, 2025

Copy link
Copy Markdown
Member

@sirosen it should be doable to take over this and merge before the release.

@webknjaz

webknjaz commented Aug 8, 2025

Copy link
Copy Markdown
Member

I wonder if x86-64 this still makes sense with GH taking away the native test env from FOSS: actions/runner-images#12520.

@sirosen

sirosen commented Aug 8, 2025

Copy link
Copy Markdown
Contributor

After reading the runner-images thread, I looked at some other CI services to see if GitHub is an outlier here. It seems that there's a broader mass migration off of support for Intel Macs. For example, this was CircleCI's announcement thread for removal of x86-64.

My current thinking is that we may have to accept the loss of a testing platform here, and hope that our coverage is still good enough. We're already in a version of this position given that our CI runs only on macos-latest.

I'm undecided about what to do with this PR exactly. I would like to be intentional about changing the job names if we're doing that (which this currently does). And I'm overall not sure what my position is around use of -latest. When reading CI output, I'd rather see macos-15 than macos-latest, but when maintaining CI config it's nice to have things update automatically.
@webknjaz, do you have a strong preference about use of latest? That might help guide my thinking on how to rebase/refactor this.

@webknjaz

webknjaz commented Aug 8, 2025

Copy link
Copy Markdown
Member

Yep, I want static version identifiers, not -latest. They are pain to predict sometimes.

We might either lose x86_64 or try to see if Rosetta works..

@webknjaz

Copy link
Copy Markdown
Member

With CPython downgrading intel macs to tier 2 (python/cpython#137638), we shouldn't attempt spending an unjustified amount of resources on it either, I suppose.

@sirosen

sirosen commented Aug 19, 2025

Copy link
Copy Markdown
Contributor

I think I'll pick this up, rebase it into a new PR, and switch us over to explicit labels for the latest runners.

If we wanted to add a job to the matrix which runs under Rosetta, we could try, but I don't have relevant experience, so I don't want to block CI cleanup on that -- treat it as a potential CI enhancement instead.


Aside: I got the sense that the CPython decision was motivated in part by your investigation. πŸ‘ nice work keeping people informed!

@webknjaz

Copy link
Copy Markdown
Member

Ack. Agreed 🀝

@webknjaz

webknjaz commented Oct 2, 2025

Copy link
Copy Markdown
Member

@sirosen looks like GH walked back on taking macos intel from us. Just got an email a couple of hours ago that they've made macos-15-intel and the intel support will be dropped in 2027.

@sirosen

sirosen commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

This has been on my TODO list, and it looks like there are new macOS runners we can use:
https://github.blog/changelog/2026-02-26-macos-26-is-now-generally-available-for-github-hosted-runners/

macos-26 is ARM
macos-26-intel is Intel

I'll try to make time to go after this, and try these new runner types.

@webknjaz webknjaz mentioned this pull request Apr 2, 2026
3 of 4 tasks
@webknjaz

webknjaz commented Apr 2, 2026

Copy link
Copy Markdown
Member

Resolved by #2348

@webknjaz webknjaz closed this Apr 2, 2026
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.

[TODO][CI] Add macOS 14 ARM 64 to the matrix

3 participants