Note: We now have a self-hosted CI runner on a Mac M1, and as of https://github.com/pantsbuild/pants/pull/15738 it's building macOS ARM64 wheels. So no more ad-hoc manual building by Eric on an M1 laptop. Every release should now automatically include M1 support.

Thank you 😭 now just to wait until we're mostly done releasing for 2.11 so that I can finally upgrade to the new macOS.... (I've held off to not require our users to be using newest macOS)

@happy-kitchen-89482 recapping as a blog post would also be a nice service to the broader community and might bring some new readers into the blog site.

a very nice follow up to https://blog.pantsbuild.org/how-we-added-apple-silicon-support-to-pants/

Yes I have already been working on that blog post. Great minds think alike.

seems to have worked…? https://pypi.org/project/pantsbuild.pants/2.13.0.dev5/#files @hundreds-father-404: are you able to check?

It did not work for me:

macosx_12_0_arm64.whl

vs

macosx_11_0_arm64.whl

. I'm an 11.0 user, so can't consume 12.0 @happy-kitchen-89482 can we use an older macOS version? I will do a manual release now

Possibly, but it means setting up a new machine which is not trivial.

Okay -- then we need to decide if Pants 2.13 drops support for macos 11.0. That puts me in a pickle as a maintainer: I must stay on 11.0 to not force all our users to be using 12.0+, so I can't upgrade as long as we release M1 wheels for anything before Pants 2.13 But I also now can't consume Pants 2.13+

It may be OK to require that for M1s at least? Do we know of M1 users still on 11.0? Apple does aggressively push users to upgrade...

to be clear: we don’t need both 11.0 and 12.0: only 11.0, since it is forwards compatible

If we change to 12.0, then I think we need to be consistent that all new Pants releases will be 12.0+, even for past Pants versions like 2.9. Otherwise, I'm stuck in the catch 22