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
#8713
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Maintainer merge checklist
Component: xxx
label.api-deprecation
orapi-break
label.release-highlight
label to be highlighted in release notes.versionadded
,versionchanged
as needed.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-latest
onkivy/kivy
repo is already targetingmacos-14
, which is an Apple Silicon runner.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 amacos-14
image that runs on Intel Macs, but is quite pricey for us.What will be the future of
apple-silicon-m1
runner hardware?