Sunset `apple-silicon-m1` self-hosted runner, as now is supported by Github Hosted runners via `macos-latest` tag. Use `macos-13` for runs on Intel macs #909
Therefore, our self-hosted apple-silicon-m1 runner, after ~1.5 years of service will start the sunset phase.
However, now comes an additional issue: "How can we make sure to properly test things for Intel Macs?".
As ATM https://github.com/orgs/community/discussions/116568, is still unanswered, targeting macos-13 for testing on an Intel runner looks like the best (free of charge) choice.
I guess the long-time alternative is macos-latest-large, which is a macos-14 image that runs on Intel Macs, but is quite pricey for us.
What will be the future of apple-silicon-m1 runner hardware?
The time has come, as being announced in https://github.blog/changelog/2024-04-01-macos-14-sonoma-is-generally-available-and-the-latest-macos-runner-image ,
macos-latestonkivy/kivyrepo is already targetingmacos-14, which is an Apple Silicon runner.Therefore, our self-hosted
apple-silicon-m1runner, after ~1.5 years of service will start the sunset phase.However, now comes an additional issue: "How can we make sure to properly test things for Intel Macs?".
As ATM https://github.com/orgs/community/discussions/116568, is still unanswered, targeting
macos-13for testing on an Intel runner looks like the best (free of charge) choice. I guess the long-time alternative ismacos-latest-large, which is amacos-14image that runs on Intel Macs, but is quite pricey for us.What will be the future of
apple-silicon-m1runner hardware?Similar PRs: https://github.com/kivy/kivy/pull/8713 , https://github.com/kivy/python-for-android/pull/3011