2024 GitHub Actions macOS runner image roadmap #9255
Comments
|
One question that doesn't seem to be addressed anywhere (and I realize this was just published today and doesn't have all the details): When macOS-14 becomes latest, does that mean all macOS runners will move to M1 instances, or will macOS-14 be available on Intel-based runners? |
|
@dpogue according to the announcement macOS-14 agents will run exclusively on M1 vCPUs
|
|
@Steve-Glass is there any timeline for macOS-14 to be deployed on Azure DevOps? |
I have the same question. It would be great to have the macos-14 build agent available in Azure DevOps. |
|
+1 regarding |
|
Are their any plans to add docker? |
Following the GitHub runner roadmap: actions/runner-images#9255 fixes #1508
Following the GitHub runner roadmap: actions/runner-images#9255 fixes #1508
Following the GitHub runner roadmap: actions/runner-images#9255 fixes #1508
Following the GitHub runner roadmap: actions/runner-images#9255 fixes #1508
Macos 13 stays on x86, macos 14 will be on arm64 See: actions/runner-images#9255 And: actions/runner-images#9254
Macos 13 stays on x86, macos 14 will be on arm64. Unfortunately arm64 mac runners don't support virtualization: https://docs.github.com/en/actions/using-github-hosted-runners/about-larger-runners/about-larger-runners#limitations-for-macos-larger-runners See: actions/runner-images#9255 And: actions/runner-images#9254
Following the GitHub runner roadmap: actions/runner-images#9255 fixes #1508
|
Is there any roadmap for supporting xcode 15 as the default on the macOS-13 image? I appreciate this may not be the correct place to ask, but was just curious as Apple is requiring xcode 15 for app store apps as of 29th April, and I wanted to see if we will need to manually set the version in our xcode v5 task. |
|
Good timing! Xcode 15 is the default in the runner image currently being rolled out: |
|
Wow! That was fast! ;) Excellent news, thanks very much. :) |
Curious about this as well. Currently they are M1 only, which is better than nothing! But would love intel macOS 14 runners to be holistic 😄 |
CI: Update macos images to macos-13 This changes the CI workflows to use `macos-13` instead of `macos-latest`. `latest` is currently `macos-12`, but GitHub is [migrating](https://github.blog/changelog/2024-04-01-macos-14-sonoma-is-generally-available-and-the-latest-macos-runner-image/) latest to `macos-14` starting immediately. 14 switches to aarch64 which we do not want, yet. rust-lang/rust already migrated to macos-13 a little while ago in rust-lang/rust#113544. This might have some performance improvements here, as the macos-12 images inconsistently have SIP enabled, but macos-13 seems to reliably have it disabled. We do not yet know when GitHub will be retiring their x86_64 runners. Their current roadmap, posted at actions/runner-images#9255, shows macos-13 supported through at least the end of the year. However, I suspect next year might spell the end for it. At that time, the Rust project might need to consider downgrading x86_64-apple-darwin to tier 2 or figure out some other option.
Now github actions only supports m1 builds (actions/runner-images#9255) and older versions of ghc are not compatible with that The problem is that the version of llvm is too new, we could try to install an older version of llvm
Now github actions only supports m1 builds (actions/runner-images#9255) and older versions of ghc are not compatible with that The problem is that the version of llvm is too new, we could try to install an older version of llvm
|
This seems to be the only announcement about MacOS-11 being removed. If that is going ahead in June, shouldn't it be mentioned in the annoucement section at the top of https://github.com/actions/runner-images/blob/main/images/macos/macos-11-Readme.md |
Per the 'roadmap' announced in actions/runner-images#9255, macos-latest now points to macos-14 as of Q2, and the macos-14 image does not supply any version of PostgreSQL. Bad news for the quick workflow that relies on the runner's installed version. Limit the MacOS CI to the macos-12 runner for now. That should hold until the image is removed in Q4. A workflow that installs a specified PostgreSQL version may be needed after that. Also, shorten the name of the workflow. It was too long to read in the online display of checks. And add a restrictive permissions: entry, which was missing, and its absence is not secure-by-default.
Breaking changes
Updates to the macOS runner image release cycle were published today, along with the macOS 14 announcement. In addition, the roadmap for calendar year 2024 has been presented below. This announcement will be updated with links to public roadmap objectives as they become publicly available.
Target date
N/A
The motivation for the changes
N/A
Possible impact
N/A
Platforms affected
Runner images affected
Mitigation ways
N/A
The text was updated successfully, but these errors were encountered: