-
Notifications
You must be signed in to change notification settings - Fork 3k
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-latest workflows will use macOS-11 #4060
Comments
This should probably be given higher priority or a sooner release date, with iOS 15 becoming widely available to end users on September 20. In our experience the iOS 15 betas are already requiring the new digital signatures that only seem to be available in Xcode 12.5.x, so any Apple Enterprise program users signing applications with the It appears that Xcode 12.5.x is only available on the macos-11 image and Apple doesn't support it on Catalina aka 10.15 so either you will have a LOT of customers using the default |
When I compiled the ios version of the flutter project on actions, the script script of the ios project got stuck. Stuck at the last script running. I was stuck for six hours and was eventually cancelled because time ran out.
|
@zi6xuan feel free to create a new issue and we will try to help you |
Meanwhile, this forum post highlights the iOS re-signing details on macOS 10.15 / Xcode 12 to solve the new signature issues on iOS 15 devices: |
FWIW the first R-4.1.1.pkg link for Intel based Macs at https://cloud.r-project.org/bin/macosx/ does support Big Sur (I have been using it on Big Sur myself for months now), however the explanatory text does not seem to have been updated to reflect this. |
@jimhester feel free to open Add request in this repo and we will add R to the Big Sur image. |
Just out of curiosity - why does this update take so long after new iOS and MacOS has been already officially released by Apple? I mean, If it's gonna be done by November 3rd it's gonna be +/- 3 months without proper GitHub support for this kind of environments. |
Python 3.6 will be unavailable on the to-be introduced macOS-11 default. Xref actions/runner-images#4060.
GitHub is currently migrating its macos-latest runner to macOS 11: actions/runner-images#4060 Unfortunately, installing VirtualBox and Vagrant on this new version of macOS is not easy, and the current macos11 runner does not support running virtual machines using Vagrant. This issue is being fixed on actions/runner-images#4010 . Until this Pull Request is merged, use macos10 runner instead of macos-latest, to continue using Vagrant to run the SELinux testsuite in a virtual machine. Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org>
GitHub is currently migrating its macos-latest runner to macOS 11: actions/runner-images#4060 Unfortunately, installing VirtualBox and Vagrant on this new version of macOS is not easy, and the current macos-11 runner does not support running virtual machines using Vagrant. This issue is being fixed on actions/runner-images#4010 . Until this Pull Request is merged, use macos-10.15 runner instead of macos-latest, to continue using Vagrant to run the SELinux testsuite in a virtual machine. Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org>
GitHub is currently migrating its macos-latest runner to macOS 11: actions/runner-images#4060 Unfortunately, installing VirtualBox and Vagrant on this new version of macOS is not easy, and the current macos-11 runner does not support running virtual machines using Vagrant. This issue is being fixed on actions/runner-images#4010 . Until this Pull Request is merged, use macos-10.15 runner instead of macos-latest, to continue using Vagrant to run the SELinux testsuite in a virtual machine. Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org>
- ansible-lint issue ansible/ansible-lint#1795 - vagrant pin macos version per actions/runner-images#4060
#1683) - ansible-lint issue ansible/ansible-lint#1795 - vagrant pin macos version per actions/runner-images#4060
The migration is completed — all the jobs on |
My job doesn't run yet on macos-11 https://github.com/goblinengine/goblin/actions/runs/1730824706 |
@filipworksdev the build took place 6 days ago, we finished the migration yesterday |
Marian does not compile on macOS 11.6, so the build has stopped working due to an upgrade from macOS-10.15 to macOS 11.6 in Azure Pipelines: actions/runner-images#4060 This PR explicitly set macOS 10.15 in the workflow.
What about macOS 12? |
@iMonZ @miketimofeev Guys you were right. Everything is done. The build was old. I did a fresh build and is all been ported. Is all good . Thank you everyone! Now I can finally use C++17 for iOS 👍 |
The macos-latest label moved to macOS 11. However, this image from GitHub doesn't have VirtualBox installed, and it's not clear that this will ever happen. 10.15 is still supported, though. These two issues are provided as reference: - actions/runner-images#4060 - actions/runner-images#4010
Use macos 10.15 since they're with vagrant and virt but don't use 11 and never due to missing vagrant on them. Ref: actions/runner-images#4060 actions/runner-images#4010 Signed-off-by: Arnaud Patard <apatard@hupstream.com>
Use macos 10.15 since they're with vagrant and virt but don't use 11 and never due to missing vagrant on them. Ref: actions/runner-images#4060 actions/runner-images#4010 Signed-off-by: Arnaud Patard <apatard@hupstream.com>
The "macos-11" image which is becoming "macos-latest" does not include virtualbox/vagrant yet. cf actions/runner-images#4060 and actions/runner-images#4010
The "macos-11" image which is becoming "macos-latest" does not include virtualbox/vagrant yet. cf actions/runner-images#4060 and actions/runner-images#4010
This trivial change introduces matrix for multiple macOS systems. For difference between `macos-10.15` and `macos-11`, see actions/runner-images#4060
GitHub is currently migrating its macos-latest runner to macOS 11: actions/runner-images#4060 Unfortunately, installing VirtualBox and Vagrant on this new version of macOS is not easy, and the current macos-11 runner does not support running virtual machines using Vagrant. This issue is being fixed on actions/runner-images#4010 . Until this Pull Request is merged, use macos-10.15 runner instead of macos-latest, to continue using Vagrant to run the SELinux testsuite in a virtual machine. Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org> Acked-by: Ondrej Mosnacek <omosnace@redhat.com>
Breaking changes
macOS-11 is ready to be the default version for the "macos-latest" label in GitHub Actions and Azure DevOps.
Target date
This change will be rolled out over a period of several weeks beginning on September, 15. We plan to complete the migration by
November, 3December, 13January 14.The motivation for the changes
GitHub Actions and Azure DevOps have supported macOS-11 in preview mode since October 2020, and starting from August 2021 macOS-11 is generally available for all customers. For almost a year we have monitored customer feedback to improve the macOS-11 image stability and now we are ready to set it as the latest.
Possible impact
The macOS-11 image has a different set of software than macOS-10.15. The most significant changes are listed in the table below:
11
12
13
11
3.5
3.6
3.7
3.8
3.9
3.8
3.9
3.6
3.7
3.7
1.14
1.15
1.16
1.17
1.16
1.17
12.3
12.2
12.1.1
12.1
12.0.1
11.7
11.6
11.5
11.4.1
11.3.1
11.2.1
10.3
12.5.1 (default)
12.5
12.4
11.7
Virtual environments affected
Mitigation ways
If you see any issues with your workflows during this transition period:
The text was updated successfully, but these errors were encountered: