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
Xcode 16.0 will be replaced by Xcode 16.2 in both macOS-14 Intel and ARM images.
Target date
Image deployment will start on January 6, 2025 and will take 3-4 days.
The motivation for the changes
This is to keep in accordance with our support policy for macOS14:
Will include all minor releases of Xcode 15 with the full platform tools suite.
Will now also include two minor releases of Xcode 16 (excluding visionOS tools). These will follow a “last two” principle, with the oldest replaced by the newest as updates are released. Beta versions will not be included.
Possible impact
Workflows based on Xcode 16.0 will fail.
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
Upgrade from Xcode 16.0 to Xcode 16.1 or 16.2 to continue with the workflows.
The text was updated successfully, but these errors were encountered:
Breaking changes
Xcode 16.0 will be replaced by Xcode 16.2 in both macOS-14 Intel and ARM images.
Target date
Image deployment will start on January 6, 2025 and will take 3-4 days.
The motivation for the changes
This is to keep in accordance with our support policy for macOS14:
Will include all minor releases of Xcode 15 with the full platform tools suite.
Will now also include two minor releases of Xcode 16 (excluding visionOS tools). These will follow a “last two” principle, with the oldest replaced by the newest as updates are released. Beta versions will not be included.
Possible impact
Workflows based on Xcode 16.0 will fail.
Platforms affected
Runner images affected
Mitigation ways
Upgrade from Xcode 16.0 to Xcode 16.1 or 16.2 to continue with the workflows.
The text was updated successfully, but these errors were encountered: