Add macOS 13 runner image

[Brett-Best]

Tool name

macOS 13

Tool license

https://www.apple.com/au/legal/sla/

Add or update?

• [X] Add
• [ ] Update

Desired version

13 RC (22A379)

Approximate size

No response

Brief description of tool

Latest major macOS version released by Apple.

URL for tool's homepage

https://developer.apple.com/documentation/macos-release-notes/macos-13-release-notes

Provide a basic test case to validate the tool's functionality.

No response

Platforms where you need the tool

• [ ] Azure DevOps
• [X] GitHub Actions

Runner images where you need the tool

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

Can this tool be installed during the build?

No

Tool installation time in runtime

N/A

Are you willing to submit a PR?

No

[EwoutH]

As for the timing of this issue, the macOS 13 Release Candiate and Xcode 14.1 Release Candiate were released today, along with an announcement that Mac App Store submissions are now open for macOS Ventura.

This means developers will want to start testing on macOS 13, both locally and in CI.

[ddobranic]

@EwoutH , thank you for your request. New macOS-12 image with included Xcode 14.1 RC (14B47) is in release process currently.

[Brett-Best]

@ddobranic this issue is for an macOS 13 image with Xcode 14.1 RC on it - not for the current macOS 12 image.

E.g. in my workflow yml I’d have runs-on: macos-13

I would expect in this directory that a new file named macos-13-Readme.md would need to be created (among other non-trivial things).

[EwoutH]

This is the big one that needs to be done for macOS 13: https://github.com/actions/runner-images/pull/4062

[3a4oT]

Do we have ETA on this? Would be nice to avoid last year's situation where we weren't able to upgrade to the latest version of Xcode because of latest macOS was not supported.

[mikhailkoliada]

I believe @Steve-Glass may provide more info on ETA

[erencelik]

Also need ETA, we need Ventura in order to proceed our CI&CD tests

[clayellis]

I don't want to just spam with "same" — but same. We have had to temporarily set up a self-hosted runner to unblock ourselves.

[cagri21]

I also don’t want to spam but we also need Ventura in order to proceed our CI&CD tests

[halonsoluis]

With the official release of Ventura (macos13) and Xcode 14.1 this gets even more important. Could we have an ETA and a bit of a push? This ticket has been open for almost a month now and every build using Swift 5.7 features is failing.

EDIT:

macos-12 image has Xcode 14.1, so projects with Swift 5.7 are able to run there. Notice that macos-latest points to macos11. I read around that this will change soon, but for a safe bet, just use macos-12.

If your project really depends on macos13 features, then we are out of luck for now.

[Brett-Best]

Two weeks later and no further information provided by GitHub ☹️

[dockay]

Bump here too, would be nice to have macOS-13 asap.

[hassila]

Yes, this is a blocker for our projects using Swift 5.7 features - not possible to deploy those on GitHub runners (and we'd like to open source a few things but it'd be great with a working CI pipeline...). So +1.

[halonsoluis]

Hi @hassila, I had the same issue, but ended up using macos-12 image

  runs-on: macos-12

It has Xcode14, so it's OK to work with.

[hassila]

No, we use features which are only available with the Ventura Swift runtime (distributed actors, duration/instant/clock, ...) so macos-12 is a no-go unfortunately.

[hakonk]

Hi @Steve-Glass ! Any news on the timeline for when MacOs 13 will be made available?

[Steve-Glass]

👋 We are targeting Q2 2023 – Apr-Jun for public beta. The public roadmap will be updated after December 15th with this objective. The plan is to open the beta runner image to all developers without any sign-up process.

[gereons]

@Steve-Glass thanks for the info. Are there any plans to speed this process up for the predictable upcoming releases of macOS?

[Brett-Best]

Wow that’s a long time away, while Xcode 14.3 beta isn’t out yet (perhaps next week) previous releases have required the next major OS version. This was an issue with both macOS 11 and macOS 12.

@gereons after delayed releases of macOS 11 and macOS 12, assurances were provided that it would be improved. Based on the timeline provided, it appears it could actually be worse this time around with macOS 13. 😬

I think it’s fair to conclude GitHub doesn’t prioritise macOS/iOS CI/CD at all.

The comments in https://github.com/actions/runner-images/issues/3649 are unfortunately still very relevant.

[halonsoluis]

Maybe time to consider other options from the competition, many customers of GitHub Actions that need this update will have no other choice.

[sladewatkins]

👋 We are targeting Q2 2023 – Apr-Jun for public beta. The public roadmap will be updated after December 15th with this objective. The plan is to open the beta runner image to all developers without any sign-up process.

With all due respect @Steve-Glass, this time-frame is when developers focus on the next version of macOS (at this time, 14). I agree with @Brett-Best, who said:

[...] after delayed releases of macOS 11 and macOS 12, assurances were provided that it would be improved. Based on the timeline provided, it appears it could actually be worse this time around with macOS 13. 😬 I think it’s fair to conclude GitHub doesn’t prioritise macOS/iOS CI/CD at all.

A lot of developers (including myself) need this, in some cases to do our jobs. This deals a massive blow to us.

[clayellis]

For reference, the public roadmap issue that @Steve-Glass mentioned above is here: https://github.com/github/roadmap/issues/620

[billnbell]

+1 on getting this done! We needed it 3 months ago.

[leofolive]

Cool, github doesn't prioritize running github actions on macos, when Apple release new version of macOs, maybe Github upgrade to ventura. Definitely should get out of github actions.

This image should be available no later than 1 week after the release of ventura.

[Brett-Best]

Wow that’s a long time away, while Xcode 14.3 beta isn’t out yet (perhaps next week) previous releases have required the next major OS version. This was an issue with both macOS 11 and macOS 12.

Xcode 14.3b1 is now out and it requires macOS 13.

[clayellis]

@Steve-Glass in an attempt to be productive and not just throw shade your team's way — can we maybe start some discourse around this issue? Some visibility into why it takes so long for GitHub to publish updated macOS runners might be helpful in quelling the mob. Is there some complex technical issue that we're all unaware of? Does it take a while to validate? Is it a planning or resources issue? Is there a blocking dependency on some other system? Is it virtual and/or physical hardware upgrades that need to happen first?

[BrianVTruong]

It'd be nice to have this sooner than later. I've been needing this for a while.

[BrentMifsud]

Is there any updates here? macOS 13 has been available for months now. Xcode 14.3 beta is out now, which drops support for macOS 12.

Why does it take GitHub almost a year after WWDC to publish the latest macOS runners?

At this rate it's probably better if we all just went to bitrise. They actually care about their devs on apples platforms.

[billnbell]

I also think you all need to respond to us. What is the status?

[3a4oT]

As said, Xcode 14.3 requires macOS 13, and we end up in the same trap as previous years. While I can understand (not really but acceptable) GitHub action CI, I don't get why Azure Pipelines (my company paying bills) are at the same level. It seems like they are using the same infrastructure, so why you can't do POC on GitHub Actions first?