-
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
[macOS] Support policy changes; Xcode 14 and 16 will be removed from macOS 14 on November 4 #10703
Comments
This is a bit messed up since |
- Days of `macos-12` are numbered: actions/runner-images#10721 Drop 5 affected jobs, replaced by `macos-15` ones added earlier today. - Drop Xcode 14 and 16 from `macos-14` jobs. Following up upstream announcement: actions/runner-images#10703 (No active jobs are affected by this.) Follow-up to 4b4ff44 #15108 Closes #15113
Can we get a response on this? |
Hey @Cheesebaron and @LotskiAndrej! We are working on adding macOS-15 to ADO, but no ETA or promises are available now. I'll publish info in #10686 once available. |
Is there any way to use Xcode 16 currently using macOS-14 ? I run task for checking Xcode version on ADO and got this, but it says it cannot locate xcode 16 |
Yes, we have not removed
Recommended task: https://learn.microsoft.com/en-us/azure/devops/pipelines/ecosystems/xcode?view=azure-devops |
Thanks for the response, but since I'm using MAUI, I cannot add xcWorkspacePath, and ADO crashes if I don't enter anything.
But it cannot locate the file |
@mjosipovic-tgr, I am currently using the same command line command you are using with macOS-14 to set it to use Xcode 16 and it works fine.
I'm using the classic pipeline editor: |
I tried it few times, changed the order of the tasks in yaml, and managed to get it to work, tnx for the responses. |
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
XCode 16 still does not seem available in the macOS-14 image?
|
@woutermeuwis please switch to |
…lvm#116216) After a recent Github Actions runner policy change [1], the version of Xcode included in the macos-14 image went from Xcode 16 to Xcode 15, breaking our build bots. This moves the bots to the macos 15 (public preview) image, which contains Xcode 16. Also, adjust an UNSUPPORTED annotation that was incorrectly targeting macos 13.7 when it should have been targeting a version of AppleClang. [1]: actions/runner-images#10703
- Work around Xcode 16 iOS test build issue: `error: Multiple commands produce '.../PlugIns'`. - Fix link error in iOS static framework test. - Update build.py to check for the right kind of build before running iOS tests on the simulator. - Update Xcode 16 build images to 'macos-15' because that's the only image that will have Xcode 16 soon. See actions/runner-images#10703.
👋 For those tracking these changes or encountering issues for the first time, here’s some context and clarification. As you may know, we recently faced significant challenges where many users began running out of disk space during tests and builds on Here’s how we’ve approached resolving the issue so far:
However, we’ve discovered that some projects rely on multiple major versions of Current Strategy 📏Our updated approach balances reducing installed
Recommendations 🦮
|
* Use macOS 13 See: actions/runner-images#10721 * Upgrade to XCode 15.2 XCode 15.2 is the default on macOS 13 * Fix unqualified call to std::move warning * Fix sprintf deprecated warnings * Upgrade macOS 14 ARM64 builds to XCode 15.4 See: actions/runner-images#10703 * Fix unused lambda capture warnings in Fader.cpp * Fix unused variable warnings * Fix formatting warning Cannot format `const void*` as a string * Force lambda conversion to function pointer
There's a recent change in GitHub hosted runners that only one major version of Xcode will be available per macOS version. See actions/runner-images#10703
|
@erik-bershel is the macos-15 for the ado now stable? I did an Android build which uses Android API level 34 on the macos-15 and got the following error below. This runs fine on the macos-14
|
Hey @amit-thapa! |
Breaking changes
Current support policy:
New support policy:
Xcode 14
andXcode 16
will be removed from themacOS-14
image.macOS-12
andmacOS-13
images. The changes will affectmacOS-14
and all subsequent images. As a result,macOS-14
-based images will contain onlyXcode 15.x
versions,macOS-15
images will contain onlyXcode 16.x
versions, and so on.Xcode
beta
is released and there is no next revision of themacOS
image? Such abeta
will be shipped as part of the latestmacOS
image that supports thisXcode
, until the next basemacOS
image is released, for example:Xcode 16
was shipped as part ofmacOS-14
until we releasedmacOS-15
.Target date
November 4, 2024
The motivation for the changes
Recently, mainly due to the introduction of the new
visionOS
platform,macOS
-based images have grown to such sizes that they are becoming more difficult to maintain, and users are experiencing difficulties with available disk space, which is critical for completing builds. Parent issue:Possible impact
Workflows based on
macOS-14
will stop running if they depend onXcode 14
and/orXcode 16
Platforms affected
Runner images affected
Mitigation ways
Users whose workflows depend on
Xcode 14
and/orXcode 16
will be forced to use themacOS-13
image forXcode-14
and themacOS-15
image forXcode-16
, respectively. Be aware thatmacos-13
YAML label refer to Intel-based image.The text was updated successfully, but these errors were encountered: