-
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 15 (Sequoia) is now available as a public beta in GitHub Actions #10686
Comments
The This breaks some pre-installed tools (e.g. Homebrew LLVM), and is a regression from See this workflow run for a reproduction: https://github.com/carlocab/workflow-test/actions/runs/11046671863 The workflow compiles a simple "hello world" We can see that We can also check directly whether OTOH, this directory exists on |
Hey @carlocab! 👋 Thank you for the info. I'll put it back with the next release. We temporary disabled it due to a |
We're seeing significantly faster build times on |
Seems that the Machine Ids are all the same and breaks some license activations for several different software programs we use for our devOps workflows. (Actually the same problem with macos-14 as well) Opened separate issue for this: |
Is I am adding macOS 15 support for one of the action linters, see rhysd/actionlint#453. |
- macos 12 is now deprecated: (actions/runner-images#10721) - macos 15 is now available: (actions/runner-images#10686)
Is there a timeline for having it available on Azure DevOps as well? |
(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
|
It is, but not all basic tools (android build tools) are available: |
Will the Azure Devops agents be transitioned to arm architecture in the future? |
macOS 15 (Sequoia) is now available as a public beta in GitHub Actions actions/runner-images#10686 https://github.com/actions/runner-images/blob/main/images/macos/macos-15-Readme.md
macOS 15 (Sequoia) is now available as a public beta in GitHub Actions actions/runner-images#10686 https://github.com/actions/runner-images/blob/main/images/macos/macos-15-Readme.md
Just a note and apologies if this is adding to the noise. .NET MAUI build which targets .NET 8 is failing with the following error:
We were forced to change the runner to macOS15 due to .NET MAUI workload dependency on Xcode 16. |
Same here |
I have the same issue. Is there a resolution to this? |
Same too. What is the workaround ? :( |
The issue with Android build-tools will be resolved with the next image update. PR: #10875 During runtime workaround should be something like that: SDKMANAGER=$ANDROID_HOME/cmdline-tools/latest/bin/sdkmanager
$SDKMANAGER "build-tools;35.0.0"
echo "$ANDROID_HOME/build-tools/35.0.0" >> $GITHUB_PATH #If you need it to be in path of course cc: @nk54, @amit-thapa, @ph |
Hey @CPRmichel!
There is no such plans at the moment. But if anything changes in our plans we'll announce it there: #8971 |
@erik-bershel when is the planned release for PR: #10875 ? |
Add this task to your pipeline yaml:
|
Thank you, even though thats sad to hear. I think it does not make sense to use Azure Devops for mobile app projects going forward. |
Hi @erik-bershel is there an ETA available now macos-15 for Azure Dev Ops? |
👋 |
Breaking changes
macOS-15
Sequoia
is now available for allGitHub Actions
.You can use the
macos-15
image label in your YAML to select this image.macOS-15 Apple Silicon
macOS-15 Intel
The image is marked as
beta
for now. It means some software can be unstable on the new platform. Also, there could be queueing issues as the capacity will be balanced only throughout the next weeks.Target date
Wednesday, September 25, 2024
The motivation for the changes
Possible impact
Software difference between macOS-14 and macOS-15
Platforms affected
Runner images affected
Mitigation ways
Please report any problems with the new image to this repository.
The text was updated successfully, but these errors were encountered: