Skip to content

Conversation

cclauss
Copy link
Contributor

@cclauss cclauss commented Oct 1, 2025

Upgrade from deprecated macos-13 GitHub Actions runner to macos-15-intel.

The currently available GitHub Actions macOS runners are:

macOS Version runner.arch
macos-13 X64
macos-14 ARM64
macos-15 ARM64
macos-15-intel X64
macos-26 ARM64
macos-latest ARM64

Should a set of test runs be made on macos-26?

Also, if: runner.os == 'Linux' -- Detecting the operating system

# Install OS specific dependencies
- name: Install Linux dependencies
if: matrix.os == 'ubuntu-latest'
if: runner.os == 'Linux'
Copy link
Member

Choose a reason for hiding this comment

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

Are we sure about this one?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes positive. The detecting the operating system link in the commit message.

# macos-13 runs on Intel
runs_on: [macos-latest, macos-13]
# macos-15-intel runs on Intel
runs_on: [macos-latest, macos-15-intel]
Copy link
Member

Choose a reason for hiding this comment

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

How about using explicit naming for both so we know what we're talking about?

Copy link
Contributor Author

@cclauss cclauss Oct 1, 2025

Choose a reason for hiding this comment

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

The names of the GitHub Actions runner images are specified in the left column of the table of the commit message. We cannot change the names of those runner images.

Copy link
Member

Choose a reason for hiding this comment

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

I mean, why not macos-15 rather than macos-latest so we're explicit about what version we're trying to run.
also any plan on running macos-14?
Also I like that the label macos-15-intel is already explicit about the architecture, that way we can remove the comment above it

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Using macos-latest is the best way to continue migrating as users do. We want CI to warn us of breakage before users do. macOS users tend to upgrade faster than users of other operating systems, so the gradual rolling upgrade that GitHub does is quite useful. We have been testing on macos-14 until this month, when macos-latest was upgraded to 15. While macos-26 is available to us, it is very recent.

If you would like, we could do: runs_on: [macos-14, macos-latest, macos-26, macos-15-intel]; however, I would avoid pinning all versions because Actions configs are often ignored until they break.

@cclauss cclauss requested a review from AndreMiras October 2, 2025 15:50
@cclauss cclauss force-pushed the patch-1 branch 2 times, most recently from 9fa79c2 to df983e0 Compare October 3, 2025 05:46
Upgrade from deprecated `macos-13` GitHub Actions runner to `macos-15-intel`.

The currently available GitHub Actions macOS runners are:
| macOS Version | runner.arch |
|---------------|-------------|
| macos-13 | X64 |
| macos-14 | ARM64 |
| macos-15 | ARM64 |
| macos-15-intel | X64 |
| macos-26 | ARM64 |
| macos-latest | ARM64 |
* Let's prepare for actions/runner-images#13046
* Like: kivy/kivy#9162

Should a set of test runs be made on `macos-26`?
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