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

The macOS 10.15 Actions runner image will begin deprecation on 5/31/22 and will be fully unsupported by 12/1/22 for GitHub and ADO #5583

Closed
1 of 8 tasks
Steve-Glass opened this issue May 20, 2022 · 27 comments · Fixed by rcsb/py-rcsb_utils_citation#4

Comments

@Steve-Glass
Copy link
Contributor

Steve-Glass commented May 20, 2022

Breaking changes

GitHub Actions is starting the deprecation process for macOS 10.15. While the image is being deprecated, You may experience longer queue times during peak usage hours. Deprecation will begin on 5/31/2022 and the image will be fully unsupported by 12/1/22

To raise awareness of the upcoming removal, we will temporarily fail jobs using macOS 10.15. Builds that are scheduled to run during the brownout periods will fail. The brownouts are scheduled for the following dates and times:

GitHub Actions:

  • August 26, 14:00 UTC - August 26, 18:00 UTC
  • September 2, 14:00 UTC - September 2, 18:00 UTC
  • September 16, 14:00 UTC - September 16, 18:00 UTC
  • September 23, 14:00 UTC - September 23, 18:00 UTC
  • October 7, 14:00 UTC - October 7, 20:00 UTC
  • October 14, 14:00 UTC - October 14, 20:00 UTC
  • October 21, 14:00 UTC - October 21, 20:00 UTC
  • October 28, 14:00 UTC - October 28, 20:00 UTC
  • November 4, 14:00 UTC - November 4, 20:00 UTC
  • November 11, 14:00 UTC - November 11, 20:00 UTC
  • November 18, 14:00 UTC - November 18, 20:00 UTC
  • November 25, 14:00 UTC - November 25, 20:00 UTC

Azure DevOps

  • August 1, 12:00 UTC - August 1, 14:00 UTC
  • August 9, 16:00 UTC - August 9, 18:00 UTC
  • August 17, 14:00 UTC - August 17, 18:00 UTC
  • August 25, 14:00 UTC - August 25, 20:00 UTC
  • September 2, 12:00 UTC - September 2, 22:00 UTC
  • September 8, 00:00 UTC - September 9, 00:00 UTC
  • September 14, 00:00 UTC - September 15, 00:00 UTC
  • September 20, 00:00 UTC - September 21, 00:00 UTC
  • September 26, 00:00 UTC - September 27, 00:00 UTC
  • October 14, 14:00 UTC - October 14, 20:00 UTC
  • October 21, 14:00 UTC - October 21, 20:00 UTC
  • October 28, 14:00 UTC - October 28, 20:00 UTC
  • November 4, 14:00 UTC - November 4, 20:00 UTC
  • November 11, 14:00 UTC - November 11, 20:00 UTC
  • November 18, 14:00 UTC - November 18, 20:00 UTC
  • November 25, 14:00 UTC - November 25, 20:00 UTC

Target date

12/1/2022

The motivation for the changes

GitHub Actions maintains the latest two stable versions of any given OS version.

Possible impact

Workflows using the macos-10.15 image label should be updated to macos-latest, macos-11, or macos-12.

Virtual environments 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

N/A

@mayeut
Copy link

mayeut commented May 21, 2022

@Steve-Glass,

does it mean that macOS-12 will be out of BETA status by then ? #5446
does it mean that macOS-latest will transition to macOS-12 in that period ?

what to do about #4010 ? It was closed and users of virtual box were told to stick on macOS-10.15 with no other alternatives proposed.

@miketimofeev
Copy link
Contributor

@mayeut yes, most likely macOS-12 will be out of beta and macOS-latest will be transitioned to macOS-12.
It looks like macOS-12 doesn't have the issue with VirtualBox, we are going to add it here #5594

yodaldevoid added a commit to yodaldevoid/ssh2-rs that referenced this issue May 29, 2022
It doesn't look like there are any provided macOS 10.14 runners left so
CI never fully completes. 10.15 is also being depreciated on 5/31/2022
(in two days at the time of writing), so there is little reason to
update to that.

macOS 10.15 depreciation issue:
actions/runner-images#5583
yodaldevoid added a commit to alexcrichton/ssh2-rs that referenced this issue May 29, 2022
It doesn't look like there are any provided macOS 10.14 runners left so
CI never fully completes. 10.15 is also being depreciated on 5/31/2022
(in two days at the time of writing), so there is little reason to
update to that.

macOS 10.15 depreciation issue:
actions/runner-images#5583
@miketimofeev miketimofeev pinned this issue Jun 23, 2022
strager added a commit to quick-lint/quick-lint-js that referenced this issue Jul 1, 2022
GitHub is deprecating their macOS 10.15 VMs [1]. Switch to the latest
supported version of macOS (12) for builds.

[1] actions/runner-images#5583
strager added a commit to quick-lint/quick-lint-js that referenced this issue Jul 1, 2022
GitHub is deprecating their macOS 10.15 VMs [1]. Switch to the latest
supported version of macOS (12) for builds.

-Wfallback isn't supported by Clang 13 and newer, so drop it from the
warning set.

[1] actions/runner-images#5583
@jlosito
Copy link

jlosito commented Jul 1, 2022

@miketimofeev the macOS 10 runners had vagrant installed on them while the macOS 12 runners do not. I'm able to install vagrant via brew on the v12 runners without issue, but brew bundle is unable to pin versions in the same way I could expect a certain version to be pre-installed on the runner. Are there plans to include the vagrant package in the v12 runners like they were on the v10 runners?

strager added a commit to quick-lint/quick-lint-js that referenced this issue Jul 1, 2022
GitHub is deprecating their macOS 10.15 VMs [1]. Switch to the latest
supported version of macOS (12) for builds.

-Wfallback isn't supported by Clang 13 and newer, so drop it from the
warning set.

[1] actions/runner-images#5583
strager added a commit to quick-lint/quick-lint-js that referenced this issue Jul 1, 2022
GitHub is deprecating their macOS 10.15 VMs [1]. Switch to the latest
supported version of macOS (12) for builds.

[1] actions/runner-images#5583
strager added a commit to quick-lint/quick-lint-js that referenced this issue Jul 1, 2022
GitHub is deprecating their macOS 10.15 VMs [1]. Switch to the latest
supported version of macOS (12) for builds.

[1] actions/runner-images#5583
@miketimofeev
Copy link
Contributor

@jlosito sure, there are no objections now. I opened a PR here #5854

kubkon added a commit to ziglang/zig that referenced this issue Jul 15, 2022
The currently used image is getting deprecated and every user is advised
to switch to either macos-11 or macos-12. The link to upstream
issue/notification:

actions/runner-images#5583
kubkon added a commit to ziglang/zig that referenced this issue Jul 15, 2022
The currently used image is getting deprecated and every user is advised
to switch to either macos-11 or macos-12. The link to upstream
issue/notification:

actions/runner-images#5583
Hiroshiba pushed a commit to VOICEVOX/voicevox_core that referenced this issue Jul 17, 2022
macos-10.15がdeplecatedになっていたためCIテストからとりのぞいた

actions/runner-images#5583
McMartin added a commit to McMartin/FRUT that referenced this issue Jun 4, 2023
The `macOS-10.15` image was removed on 2023-03-31 [1], and the
`ubuntu-18.04` image was removed on 2023-04-03 [2].

[1]: actions/runner-images#5583 (comment)
[2]: actions/runner-images#6002 (comment)
McMartin added a commit to McMartin/FRUT that referenced this issue Jun 4, 2023
The `macOS-10.15` image was removed on 2023-03-31 [1], and the
`ubuntu-18.04` image was removed on 2023-04-03 [2].

[1]: actions/runner-images#5583 (comment)
[2]: actions/runner-images#6002 (comment)
xorcare added a commit to xorcare/dotfiles that referenced this issue Jun 6, 2023
The macOS-10.15 environment is deprecated, consider switching to
macos-11(macos-latest), macos-12 instead. For more details see
actions/runner-images#5583
xorcare added a commit to xorcare/dotfiles that referenced this issue Jun 6, 2023
The macOS-10.15 environment is deprecated, consider switching to
macos-11(macos-latest), macos-12 instead. For more details see
actions/runner-images#5583
OskarElek pushed a commit to PolyPhyHub/PolyPhy that referenced this issue Jun 8, 2023
* Added a flag file to differentiate between workflow tests
* Made changes in notebook dir path and few minor changes in notebook
itself
* Added few requirements which were required for staging notebook
* Upgraded macOS versions as previous ones are deprecated [read issue
here](actions/runner-images#5583)

Closes #41

---------

Authored-by: pjflux2001 <[email protected]>
leonlynch added a commit to leonlynch/libargp that referenced this issue Jul 23, 2023
Github has deprecated the runner image for MacOS 10.15. See
actions/runner-images#5583
drojf added a commit to 07th-mod/ponscripter-fork that referenced this issue Sep 17, 2023
drojf added a commit to 07th-mod/ponscripter-fork that referenced this issue Sep 29, 2023
drojf added a commit to 07th-mod/ponscripter-fork that referenced this issue Sep 29, 2023
jkaving added a commit to jkaving/opencv that referenced this issue Oct 12, 2023
macOS 10.15 runners for GitHub Actions have been deprecated:
actions/runner-images#5583
gittup added a commit to gittup/tup that referenced this issue Jan 25, 2024
FUSE doesn't work anymore here, so it just continually fails. See:
actions/runner-images#5583 (comment)
jhlegarreta added a commit to jhlegarreta/ITKModuleTemplate that referenced this issue Jul 2, 2024
Switch Github Actions macOS environment version to `macos-11`.

`macOS-10.15` is being deprecated and supported will end by 8/30/2022:
actions/runner-images#5583

Related to recent warnings in the Azure Pipelines macOS environment
being used in the main ITK repository:
InsightSoftwareConsortium/ITK@e5595de
nevans added a commit to nevans/eventmachine that referenced this issue Sep 3, 2024
* GitHub Actions dropped suuport for macos-10.15 on 2022-12-01:
  actions/runner-images#6002
* GitHub Actions dropped suuport for ubuntu-18.04 on 2023-04-03:
  actions/runner-images#5583

Although there are benefits to testing EventMachine with these older OS
versions—especially given EventMachine's legacy status and the types of
projects which are most likely to depend on it—there are also
significant costs to maintaining CI for them once GitHub Actions has
dropped support.
nevans added a commit to nevans/eventmachine that referenced this issue Sep 3, 2024
* GitHub Actions dropped suuport for macos-10.15 on 2022-12-01:
  actions/runner-images#6002
* GitHub Actions dropped suuport for ubuntu-18.04 on 2023-04-03:
  actions/runner-images#5583

Although there are benefits to testing EventMachine with these older OS
versions—especially given EventMachine's legacy status and the types of
projects which are most likely to depend on it—there are also
significant costs to maintaining CI for them once GitHub Actions has
dropped support.
nevans added a commit to nevans/eventmachine that referenced this issue Sep 3, 2024
GitHub Actions dropped support for macos-10.15 on 2022-12-01:
- actions/runner-images#5583

Under the presumption that MacOS is primarily used for development and
not for deployment, I've switched the macos GitHub Actions runners to
use the "latest" release version for ruby >= 2.6.  Earlier ruby's don't
support arm64, so they are using the macos-13 runner (which is amd64).

On the one hand, this is less explicit and is no longer "pinned", so it
may result in CI failing when GitHub Actions updates these runners.  On
the other hand, we also won't need another PR to update these every time
an old version is dropped or a new version is added.

I attempted to make the same change from windows-2019 to windows-latest.
But I saw three tests that reliably pass under windows-2019 and reliably
fail under windows-2022.  Since I don't have a Windows OS dev env at my
disposal, I'm opting to just let windows CI continue under windows-2019,
for now.
5eqn pushed a commit to 5eqn/nih-plug that referenced this issue Nov 11, 2024
They're disabling the macOS 10.15 runner:

actions/runner-images#5583
@MDAkash889
Copy link

I am Alpishar Akash I am from Bangladesh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.