-
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-latest workflows will use macOS-12 #6384
Comments
This is to fix the following error when running `bundle exec jazzy` in CI: > `require': cannot load such file -- rexml/document I believe that it was introduced after GitHub’s switch to macOS 12 runners (actions/runner-images#6384), which bumps the default Ruby version from 2.7 to 3.0. The error was fixed in realm/jazzy#1260.
This is to fix the following error when running `bundle exec jazzy` in CI: > `require': cannot load such file -- rexml/document I believe that it was introduced after GitHub’s switch to macOS 12 runners (actions/runner-images#6384), which bumps the default Ruby version from 2.7 to 3.0. The error was fixed in realm/jazzy#1260.
@arichorn Please see this blog post |
Thank you @wojsmol |
Alright but I already went to this site earlier today, it is a little complicated to understand GitHub’s new commands |
@arichorn Please post a link to affected workflow if you can. |
@arichorn - It would seem they forgot to include the name of the offending action into the warning message, so it can be quite cryptic. Re-run a job that shows the warning and check the box for debug logging, then you can see in the debug output which actions need to be updated. (Also - those are unrelated to this particular issue.) |
Oh alright thanks, and sorry for putting it in here |
Hey I’m back! I have successfully migrated the runner to run MacOS 12 actions, I readed the thing above and resolved it! Ty y’all |
Fixes: macOS-latest pipelines will use macOS-12 soon. For more details, see actions/runner-images#6384
Fixes: macOS-latest pipelines will use macOS-12 soon. For more details, see actions/runner-images#6384
Fixes: macOS-latest pipelines will use macOS-12 soon. For more details, see actions/runner-images#6384
Fixes: macOS-latest pipelines will use macOS-12 soon. For more details, see actions/runner-images#6384
I just found even I use But if I changed it to Maybe it still need some times to migrate (? |
@Xanonymous-GitHub hello, yes migration is in progress and it is planned to be complete by December 1st. |
Got it, thanks :) |
I want to see if there's trouble ahead from this: actions/runner-images#6384 Signed-off-by: Stephan Renatus <[email protected]>
Hey guys, I understand that you have time pressures, and it's great to see the amazing work you are doing. However, for the least six months, we have not been able to do a build using the runner. We need to support Swift 5.7, and Xcode 14. However, it took six months for this runner to even support the latest Xcode/macOS. Mac OS do YEARLY updates to their tooling. Having this run 6 months behind really is detrimental to delivery. I could understand 1 month, but 6 month delays... While there has been a BETA out for even longer. Sounds like the Mac team needs to grow a few team members. Thanks for the great work again, and hopefully we won't have to wait 6 months + for an update to the Xcode/macOS runners. |
Finally migrated: #6901! |
Thanks guys! |
Specifying `macOS-latest` results in a GH warning that "macOS-latest pipelines will use macOS-12 soon. For more details, see actions/runner-images#6384". To clean up the warnings, let's just pin to macOS-12 for now.
Specifying `macOS-latest` results in a GH warning that "macOS-latest pipelines will use macOS-12 soon. For more details, see actions/runner-images#6384". To clean up the warnings, let's just pin to macOS-12 for now.
macos-latest is macos-11 but will be macos-12 soon: actions/runner-images#6384
Specifying `macOS-latest` results in a GH warning that "macOS-latest pipelines will use macOS-12 soon. For more details, see actions/runner-images#6384". To clean up the warnings, let's just pin to macOS-12 for now.
Specifying `macOS-latest` results in a GH warning that "macOS-latest pipelines will use macOS-12 soon. For more details, see actions/runner-images#6384". To clean up the warnings, let's just pin to macOS-12 for now.
Breaking changes
macOS-12 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 October, 3. We plan to complete the migration by March, 1st, 2023.
The motivation for the changes
GitHub Actions and Azure DevOps have supported macOS-12 in public beta since April 2022, and starting from June 2022 macOS-12 is generally available for all customers. We have monitored customer feedback to improve the macOS-12 image stability and now we are ready to set it as the latest.
Possible impact
The macOS-12 image has a different set of software than macOS-11. The most significant changes are listed in the table below:
Vagrant
Support for Parallels Desktop
2.*
18.*
2.5.*
2.6.*
2.7.* default
3.0.*
3.1.*
3.0.* default
3.1.*
cocoapods,
nomad-cli,
xcpretty,
bundler,
fastlane,
jazzy
cocoapods,
xcpretty,
bundler,
fastlane,
jazzy
10.*
11.*
Platforms affected
Runner images 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: