Repository navigation
[macOS] The macOS 13 Ventura based runner images will begin deprecation on September 22nd and will be fully unsupported by December 4th for GitHub and ADO #13046
Description
Breaking changes
GitHub Actions is starting the deprecation process for macOS 13 and macOS 13 arm64. While the images are being deprecated, You may experience longer queue times during peak usage hours. Deprecation will begin on September 22nd, 2025 and the images will be fully unsupported by December 8th, 2025 for GitHub Actions and Azure DevOps.
To raise awareness of the upcoming removal, we will temporarily fail jobs using macOS 13 and macOS 13 arm64. Builds that are scheduled to run during the brownout periods will fail. The brownouts are scheduled for the following dates and times:
- November 4, 14:00 UTC - November 5, 00:00 UTC
- November 11, 14:00 UTC - November 12, 00:00 UTC
- November 18, 14:00 UTC - November 19, 00:00 UTC
- November 25, 14:00 UTC - November 26, 00:00 UTC
For users that require the x86_64 (Intel) environment, we are also introducing a new label to migrate to: macos-15-intel. The new label will run on macOS 15 and will be available from now until August 2027. This will be the last available x86_64 image from Actions, and after that date the x86_64 architecture will not be supported on GitHub Actions. For more information see this announcement: #13045
Target date
September 22 - December 4
The motivation for the changes
GitHub Actions maintains the latest two stable versions of any given OS version.
Possible impact
Workflows using the macos-13 image label will be terminated with an error.
Platforms affected
- Azure DevOps
- GitHub Actions
Runner images affected
- Ubuntu 22.04
- Ubuntu 24.04
- macOS 13
- macOS 13 Arm64
- macOS 14
- macOS 14 Arm64
- macOS 15
- macOS 15 Arm64
- macOS 26 Arm64
- Windows Server 2019
- Windows Server 2022
- Windows Server 2025
Mitigation ways
- Workflows using the
macos-13image label should be updated tomacos-latest,macos-14, ormacos-15. - Workflows that depend on
x86_64(Intel CPU) can be migrated to use themacos-15-intellabel, which is currently planned as the last supported image based on Intel CPU.
Activity
[-][macOS] The macOS 13 Ventura based runner images will begin deprecation on **September 22nd** and will be fully unsupported by **December 4th** for GitHub and ADO[/-][+][macOS] The macOS 13 Ventura based runner images will begin deprecation on September 22nd and will be fully unsupported by December 4th for GitHub and ADO[/+]ci: Change macOS runner image to macos-15-intel
switch to a newer runner for intel based MacOS, since the macos-13 on…
ci: Replace `macos-13` image with `macos-15-intel` image (GHA)
CI: update macOS runners
CI: update macOS runners (#2971)
Remove automatic tests on macos-13 github runner because of its depre…
cclauss commentedon Sep 23, 2025
chore(ci): Test on Python 3.14 release candidate 3
chore(ci): Test on Python 3.14 release candidate 3
245 remaining items
ci: switch to macos-15
fix: correct last line visibility in filtered view with text wrap ena…
build: Update mac runner
fix: correct last line visibility in filtered view with text wrap ena…
tools: drop deprecated `macos-13` runner
fix: correct last line visibility in filtered view with text wrap ena…
fix: correct last line visibility in filtered view with text wrap ena…
CI: upgrade workflows to use macos-15(*) rather than macos-13 (#2276)
Migrate to macos-15-intel runners
Xiangyu-Hu commentedon Nov 22, 2025
I have tried macos-15-intel, but it is very slow compared to macos-13.
cclauss commentedon Nov 22, 2025
A side-by-side benchmark of
macos-13andmacos-15-intelwould be quite helpful.Xiangyu-Hu commentedon Nov 22, 2025
I have run the same CI (run test cases) using macos-13 takes about 3 hours, but with
macos-15-intelfailure (beyond 6 hours) due to every case is much slower.Please also check the other issue: #12545
erik-bershel commentedon Dec 16, 2025
Closing as macOS 13 based images were disabled. 🫡
Earu commentedon Dec 30, 2025
Hi @erik-bershel, do you think it would be possible to have a runner naming convention using the
latestconvention, referencing macos-15-intel makes it so that when the next depreciation happens I'll have to dig into my CIs again to figure out why I suddenly have cancelled jobs (and probably will have forgotten about it!).Granted it doesn't happen that often and I think that in a few years it'll be safe to say that over 90% of macos users will be running arm, but I think it would be a nice QoL change and respect better the convention in place with the other runner names.