-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Add macOS 13 runner image #6426
Comments
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. |
@EwoutH , thank you for your request. New macOS-12 image with included Xcode 14.1 RC (14B47) is in release process currently. |
@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 I would expect in this directory that a new file named |
This is the big one that needs to be done for macOS 13: #4062 |
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. |
I believe @Steve-Glass may provide more info on ETA |
Also need ETA, we need Ventura in order to proceed our CI&CD tests |
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. |
I also don’t want to spam but we also need Ventura in order to proceed our CI&CD tests |
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. If your project really depends on macos13 features, then we are out of luck for now. |
Two weeks later and no further information provided by GitHub |
Bump here too, would be nice to have macOS-13 asap. |
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. |
Hi @hassila, I had the same issue, but ended up using macos-12 image
It has Xcode14, so it's OK to work with. |
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. |
Hi @Steve-Glass ! Any news on the timeline for when MacOs 13 will be made available? |
👋 We are targeting |
@Steve-Glass thanks for the info. Are there any plans to speed this process up for the predictable upcoming releases of macOS? |
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. I think it’s fair to conclude GitHub doesn’t prioritise macOS/iOS CI/CD at all. The comments in #3649 are unfortunately still very relevant. |
Maybe time to consider other options from the competition, many customers of GitHub Actions that need this update will have no other choice. |
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:
A lot of developers (including myself) need this, in some cases to do our jobs. This deals a massive blow to us. |
In a weird position here!! Just finished a contract and acquired 3 Mac minis (MacOS13 ) with MacStadium and realized we don't have a runner image ;( never thought this would be an issue!! is there any workaround for time being?? |
We are now facing issue with missing Xcode 14.3.
|
Please add a mac-13 image for azure. It is getting urgent. |
Yes please, this would help us a lot. |
In the MacOS-13 image, can you make sure to include msbuild 17? Even though we don't appear to have any blocking dependencies on new libraries in MacOS 13, we can't compile .Net 7 code on MacOS-12 because it only has msbuild 16 which can't target .Net 7. Like many people commenting above - this seems ridiculously late and is blocking many people.. |
Would it perhaps be possible to be a little more precise about the time period? We are now already between Apr - June and it would be helpful for many at least to know whether they now still have to wait 1 week or 2 months. Update: I know - 3 weeks ago I already mentioned that we all need some patience. I still support that 100%. But some of us at least need some kind of plannability. The least would be: Will it be May or June? |
macOS 13 is now available in public beta 🚀 |
macOS 13 is also available for Azure DevOps. Communications will be out this afternoon (EST). |
Hey @Steve-Glass, thanks for the update. FYI. Seems like the link with "software list" doesn't work. |
OK the Azure Node NVM does not work in the new MacOS 13. $(Agent.HomeDirectory)/scripts/select-node-version.sh node18 It does not find the |
Here is what is says
|
@billnbell raise a new issue |
OK but nvm was there in the past.
Was in https://github.com/actions/runner-images/blob/main/images/macos/toolsets/toolset-12.json |
I believe this has the same root cause as actions/setup-python#658 . That got sent over to setup-python because I was trying Python, but I don't think that's the right place for it... The issue is the hostedtoolcache isn't populated at all. |
Are the msbuild and nuget tasks expected to work on a MacOS-13 agent? 'dotnet publish' runs fine and can build our native Mac Cocoa app, but msbuild and nuget tasks die immediately with a mono not found error. MSBuild fails with: NuGet fails with: Not really clear if these tasks are supposed to be used anymore with .Net 5.0+? We used them successfully with .Net 4.7.2, but they've never worked on .Net 6.0 or .Net 7.0. The documentation doesn't seem to say you shouldn't use them anymore, but they don't work on MacOS-12 or MacOS-13 images - but the error is different on both images. On MacOS-12, the errors are related to the TargetFramework attribute, on MacOS-13, they fail with the mono not found error. |
Agreed we need toolcache
|
The page should be available now. Please submit a new issue for any concerns with existing software, or requests for new software. |
Hi All! We are aware that macOS-13 is still missing lots of software, we are also aware of what is considered the most important and desired ones. We are working on re-adding the software back! Please remember that it is still in the beta phase and things will change. Thanks for your patience! :) |
Tool name
macOS 13
Tool license
https://www.apple.com/au/legal/sla/
Add or 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
Runner images where you need the tool
Can this tool be installed during the build?
Tool installation time in runtime
N/A
Are you willing to submit a PR?
No
The text was updated successfully, but these errors were encountered: