-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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. :) |
actions/runner-images#9255 - macOS 11 is removed - macOS 14 is added
actions/runner-images#9255 - macOS 11 is removed - macOS 14 is added
actions/runner-images#9255 - macOS 11 is removed - macOS 14 is added
actions/runner-images#9255 - macOS 11 is removed - macOS 14 is added
actions/runner-images#9255 - macOS 11 is removed - macOS 14 is added
actions/runner-images#9255 - macOS 11 is removed - macOS 14 is added
actions/runner-images#9255 - macOS 11 is removed - macOS 14 is added
macOS 11 support has been dropped in the GitHub-hosted CI runners: actions/runner-images#9255. This has the unpleasant effect of breaking all our CI until this gets merged.
macOS 11 support has been dropped in the GitHub-hosted CI runners: actions/runner-images#9255. This has the unpleasant effect of breaking all our CI until this gets merged.
(ci) Update macOS Xcode to 15 This updates the macOS builders to Xcode 15. The aarch64 images will be removing Xcode 14 and 16 very soon (actions/runner-images#10703), so we will need to make the switch to continue operating. The linked issue also documents GitHub's new policy for how they will be updating Xcode in the future. Also worth being aware of is the future plans for x86 runners documented in actions/runner-images#9255 and actions/runner-images#10686, which will impact our future upgrade behaviors. I decided to also update the Xcode in the x86_64 runners, even though they are not being removed. It felt better to me to have all macOS runners on the same (major) version of Xcode. However, note that the x86_64 runners do not have the latest version of 15 (15.4), so I left them at 15.2 (which is currently the default Xcode of the runner). Xcode 15 was previously causing problems (see rust-lang#121058) which seem to be resolved now. `@bjorn3` fixed the `invalid r_symbolnum` issue with cranelift. The issue with clang failing to link seems to be fixed, possibly by the update of the pre-built LLVM from 14 to llvm 15 in rust-lang#124850, or an update in our source version of LLVM. I have run some try builds and at least LLVM seems to build (I did not run any tests). Closes rust-lang#121058
(ci) Update macOS Xcode to 15 This updates the macOS builders to Xcode 15. The aarch64 images will be removing Xcode 14 and 16 very soon (actions/runner-images#10703), so we will need to make the switch to continue operating. The linked issue also documents GitHub's new policy for how they will be updating Xcode in the future. Also worth being aware of is the future plans for x86 runners documented in actions/runner-images#9255 and actions/runner-images#10686, which will impact our future upgrade behaviors. I decided to also update the Xcode in the x86_64 runners, even though they are not being removed. It felt better to me to have all macOS runners on the same (major) version of Xcode. However, note that the x86_64 runners do not have the latest version of 15 (15.4), so I left them at 15.2 (which is currently the default Xcode of the runner). Xcode 15 was previously causing problems (see rust-lang#121058) which seem to be resolved now. `@bjorn3` fixed the `invalid r_symbolnum` issue with cranelift. The issue with clang failing to link seems to be fixed, possibly by the update of the pre-built LLVM from 14 to llvm 15 in rust-lang#124850, or an update in our source version of LLVM. I have run some try builds and at least LLVM seems to build (I did not run any tests). Closes rust-lang#121058
(ci) Update macOS Xcode to 15 This updates the macOS builders to Xcode 15. The aarch64 images will be removing Xcode 14 and 16 very soon (actions/runner-images#10703), so we will need to make the switch to continue operating. The linked issue also documents GitHub's new policy for how they will be updating Xcode in the future. Also worth being aware of is the future plans for x86 runners documented in actions/runner-images#9255 and actions/runner-images#10686, which will impact our future upgrade behaviors. I decided to also update the Xcode in the x86_64 runners, even though they are not being removed. It felt better to me to have all macOS runners on the same (major) version of Xcode. However, note that the x86_64 runners do not have the latest version of 15 (15.4), so I left them at 15.2 (which is currently the default Xcode of the runner). Xcode 15 was previously causing problems (see #121058) which seem to be resolved now. `@bjorn3` fixed the `invalid r_symbolnum` issue with cranelift. The issue with clang failing to link seems to be fixed, possibly by the update of the pre-built LLVM from 14 to llvm 15 in rust-lang/rust#124850, or an update in our source version of LLVM. I have run some try builds and at least LLVM seems to build (I did not run any tests). Closes #121058
(ci) Update macOS Xcode to 15 This updates the macOS builders to Xcode 15. The aarch64 images will be removing Xcode 14 and 16 very soon (actions/runner-images#10703), so we will need to make the switch to continue operating. The linked issue also documents GitHub's new policy for how they will be updating Xcode in the future. Also worth being aware of is the future plans for x86 runners documented in actions/runner-images#9255 and actions/runner-images#10686, which will impact our future upgrade behaviors. I decided to also update the Xcode in the x86_64 runners, even though they are not being removed. It felt better to me to have all macOS runners on the same (major) version of Xcode. However, note that the x86_64 runners do not have the latest version of 15 (15.4), so I left them at 15.2 (which is currently the default Xcode of the runner). Xcode 15 was previously causing problems (see #121058) which seem to be resolved now. `@bjorn3` fixed the `invalid r_symbolnum` issue with cranelift. The issue with clang failing to link seems to be fixed, possibly by the update of the pre-built LLVM from 14 to llvm 15 in rust-lang/rust#124850, or an update in our source version of LLVM. I have run some try builds and at least LLVM seems to build (I did not run any tests). Closes #121058
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: