You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- all OS compatible versions side-by-side
- for beta, GM versions - latest beta only
- old patch versions are deprecated in 3 months
New support policy:
- only one major version of Xcode will be supported per macOS version
- all minor versions of the supported major version will be available
- beta and RC versions will be provided "as-is" in the latest available macOS image only no matter of beta/GA status of the image
- when a new patch version is released, the previous patch version will be replaced
What does it means in general terms? Starting from the specified date, all minor versions of Xcode 14 and Xcode 16 will be removed from the macOS-14 image.
What about other images? These changes will not affect macOS-12 and macOS-13 images. The changes will affect macOS-14 and all subsequent images. As a result, macOS-14-based images will contain only Xcode 15.x versions, macOS-15 images will contain only Xcode 16.x versions, and so on.
What happens when a new major Xcodebeta is released and there is no next revision of the macOS image? Such a beta will be shipped as part of the latest macOS image that supports this Xcode, until the next base macOS image is released, for example: Xcode 16 was shipped as part of macOS-14 until we released macOS-15.
Target date
October 28, 2024
The motivation for the changes
Recently, mainly due to the introduction of the new visionOS platform, macOS-based images have grown to such sizes that they are becoming more difficult to maintain, and users are experiencing difficulties with available disk space, which is critical for completing builds. Parent issue:
Workflows based on macOS-14 will stop running if they depend on Xcode 14 and/or Xcode 16
Platforms affected
Azure DevOps
GitHub Actions
Runner images affected
Ubuntu 20.04
Ubuntu 22.04
Ubuntu 24.04
macOS 12
macOS 13
macOS 13 Arm64
macOS 14
macOS 14 Arm64
macOS 15
macOS 15 Arm64
Windows Server 2019
Windows Server 2022
Mitigation ways
Users whose workflows depend on Xcode 14 and/or Xcode 16 will be forced to use the macOS-13 image for Xcode-14 and the macOS-15 image for Xcode-16, respectively. Be aware that macos-13 YAML label refer to Intel-based image.
The text was updated successfully, but these errors were encountered:
- Days of `macos-12` are numbered:
actions/runner-images#10721
Drop 5 affected jobs, replaced by `macos-15` ones added earlier today.
- Drop Xcode 14 and 16 from `macos-14` jobs.
Following up upstream announcement:
actions/runner-images#10703
(No active jobs are affected by this.)
Follow-up to 4b4ff44#15108Closes#15113
Breaking changes
Current support policy:
New support policy:
Xcode 14
andXcode 16
will be removed from themacOS-14
image.macOS-12
andmacOS-13
images. The changes will affectmacOS-14
and all subsequent images. As a result,macOS-14
-based images will contain onlyXcode 15.x
versions,macOS-15
images will contain onlyXcode 16.x
versions, and so on.Xcode
beta
is released and there is no next revision of themacOS
image? Such abeta
will be shipped as part of the latestmacOS
image that supports thisXcode
, until the next basemacOS
image is released, for example:Xcode 16
was shipped as part ofmacOS-14
until we releasedmacOS-15
.Target date
October 28, 2024
The motivation for the changes
Recently, mainly due to the introduction of the new
visionOS
platform,macOS
-based images have grown to such sizes that they are becoming more difficult to maintain, and users are experiencing difficulties with available disk space, which is critical for completing builds. Parent issue:Possible impact
Workflows based on
macOS-14
will stop running if they depend onXcode 14
and/orXcode 16
Platforms affected
Runner images affected
Mitigation ways
Users whose workflows depend on
Xcode 14
and/orXcode 16
will be forced to use themacOS-13
image forXcode-14
and themacOS-15
image forXcode-16
, respectively. Be aware thatmacos-13
YAML label refer to Intel-based image.The text was updated successfully, but these errors were encountered: