Skip to content
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

Closed
4 of 10 tasks
ddobranic opened this issue Oct 11, 2022 · 27 comments
Closed
4 of 10 tasks

macOS-latest workflows will use macOS-12 #6384

ddobranic opened this issue Oct 11, 2022 · 27 comments

Comments

@ddobranic
Copy link
Contributor

ddobranic commented Oct 11, 2022

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:

Tool name macOS-11 macOS-12 Notes
Virtualbox
Vagrant
Support for Parallels Desktop
- 6.*
2.*
18.*
At the request of users, virtualization tools that were previously unavailable in macOS 11 had been added
Ruby toolcache 2.4.*
2.5.*
2.6.*
2.7.* default
3.0.*
3.1.*
2.7.*
3.0.* default
3.1.*
EOL Ruby versions had been removed
Ruby Gems xcode-install,
cocoapods,
nomad-cli,
xcpretty,
bundler,
fastlane,
jazzy
xcode-install,
cocoapods,
xcpretty,
bundler,
fastlane,
jazzy
nomad-cli has been removed as the project is no longer maintained.
CLang 13.0 (default) 14.0 (default) Please, pay attention to changes for default compiler
GCC / GFortran 9.*
10.*
11.*
11.* Old versions had been removed
Xamarin.iOS 13.20 - 15.8 15.0 - 16.0 Old versions and versions incompatible with the pre-installed Xcodes had been removed
Xamarin.Mac 6.20 - 8.8 7.14 - 8.12 Old versions and versions incompatible with the pre-installed Xcodes had been removed
Xamarin.Android 11.0 – 12.2 11.3 – 13.0 Old versions and versions incompatible with the pre-installed Xcodes had been removed
Xcode 13.2.1 (default)13.113.012.5.112.411.7 14.1 (beta)14.0.1 (default)14.013.2.113.113.012.5.112.411.7 Only OS-compatible versions left + the latest 11 version

Platforms affected

  • Azure DevOps
  • GitHub Actions

Runner images affected

  • Ubuntu 18.04
  • Ubuntu 20.04
  • Ubuntu 22.04
  • macOS 10.15
  • macOS 11
  • macOS 12
  • Windows Server 2019
  • Windows Server 2022

Mitigation ways

If you see any issues with your workflows during this transition period:

  • File an issue in this repository
  • Switch back to macOS 11 by specifying the “macOS-11" label. We will continue to support macOS 11.
lawrence-forooghian added a commit to ably/ably-asset-tracking-swift that referenced this issue Oct 12, 2022
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.
lawrence-forooghian added a commit to ably/ably-asset-tracking-swift that referenced this issue Oct 13, 2022
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.
@arichornlover
Copy link

I heard the news. Is there any new methods for these? These just got deprecated and it led me to this GitHub page. I will need to fix this as soon as possible if the new methods are found.
42523143-E8E7-40EC-B122-6D6758BC33FA

@wojsmol
Copy link

wojsmol commented Oct 14, 2022

@arichorn Please see this blog post

@ddobranic
Copy link
Contributor Author

Thank you @wojsmol

@arichornlover
Copy link

Alright but I already went to this site earlier today, it is a little complicated to understand GitHub’s new commands

@wojsmol
Copy link

wojsmol commented Oct 14, 2022

@arichorn Please post a link to affected workflow if you can.

@mattjohnsonpint
Copy link

mattjohnsonpint commented Oct 14, 2022

@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.)

@arichornlover
Copy link

@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

@arichornlover
Copy link

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

kcgen added a commit to dosbox-staging/dosbox-staging that referenced this issue Oct 15, 2022
Fixes:

macOS-latest pipelines will use macOS-12 soon. For
more details, see actions/runner-images#6384
kcgen added a commit to dosbox-staging/dosbox-staging that referenced this issue Oct 15, 2022
Fixes:

macOS-latest pipelines will use macOS-12 soon. For
more details, see actions/runner-images#6384
kcgen added a commit to dosbox-staging/dosbox-staging that referenced this issue Oct 15, 2022
Fixes:

macOS-latest pipelines will use macOS-12 soon. For
more details, see actions/runner-images#6384
kcgen added a commit to dosbox-staging/dosbox-staging that referenced this issue Oct 15, 2022
Fixes:

macOS-latest pipelines will use macOS-12 soon. For
more details, see actions/runner-images#6384
@Xanonymous-GitHub
Copy link

Xanonymous-GitHub commented Oct 16, 2022

I just found even I use macos-latest it still runs on v11 instead of v12 in this https://github.com/NEO-TAT/tat_flutter/actions/runs/3260016715/jobs/5353264229.

But if I changed it to macos-12, it uses 12.

Maybe it still need some times to migrate (?

@ddobranic
Copy link
Contributor Author

@Xanonymous-GitHub hello, yes migration is in progress and it is planned to be complete by December 1st.

@Xanonymous-GitHub
Copy link

Got it, thanks :)

srenatus added a commit to srenatus/opa that referenced this issue Oct 18, 2022
I want to see if there's trouble ahead from this:

actions/runner-images#6384

Signed-off-by: Stephan Renatus <[email protected]>
@realityworks
Copy link

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.

@mikhailkoliada
Copy link
Contributor

Finally migrated: #6901!

@realityworks
Copy link

Thanks guys!

Vini2 added a commit to metagentools/MetaCoAG that referenced this issue Jan 17, 2023
Vini2 added a commit to metagentools/GraphBin that referenced this issue Jan 17, 2023
Vini2 added a commit to Vini2/phables that referenced this issue Jan 17, 2023
groszewn added a commit to groszewn/tensorboard that referenced this issue Jan 20, 2023
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.
groszewn added a commit to tensorflow/tensorboard that referenced this issue Jan 20, 2023
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.
EliahKagan added a commit to EliahKagan/palgoviz that referenced this issue Jan 26, 2023
macos-latest is macos-11 but will be macos-12 soon:

actions/runner-images#6384
yatbear pushed a commit to yatbear/tensorboard that referenced this issue Mar 27, 2023
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.
dna2github pushed a commit to dna2fork/tensorboard that referenced this issue May 1, 2023
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.
Vini2 added a commit to metagentools/GraphBin that referenced this issue May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

16 participants