macOS Tahoe RC with Xcode 27.2 Now Available

The getmac-tahoe-rc image has been rebuilt. It still runs macOS Tahoe 26.6.2 (25G83), but the toolchain story has changed: Xcode 27.2 (27B52) is now the default, and ten Xcode versions are installed side by side — from 16.4 up to 27.2 — each with its Metal toolchain already mounted.
Until today this label carried two toolchains, Xcode 27.0 and 27.1. It now covers every Xcode generation we ship anywhere on the fleet, in one image.
What's New
- Xcode 27.2 is the default — Build 27B52, replacing Xcode 27.0 as the version a job gets when it doesn't select one.
- Ten Xcode versions in one label — 27.2, 27.1, 27.0, 26.6, 26.5, 26.4.1, 26.3, 26.2, 26.1 and 16.4. See below.
- The Metal toolchain is pre-installed for every Xcode 26+ version — shader builds no longer download a compiler from Apple before they compile.
- 27.2 simulator runtimes across all four platforms — iOS 27.2, tvOS 27.2, watchOS 27.2 and visionOS 27.2, alongside the 27.0, 26.x and legacy 18.x/11.x/2.x runtimes.
- Java 27.0.1 — Up from 26.0.2.1.
- Rust 1.100.0 and Go 1.27.4 — Up from 1.98.1 and 1.27.1.
- Updated CLIs — AWS CLI 2.40.3 (from 2.36.45), Google Cloud SDK 593.0.0 (from 585.0.0), and GitHub CLI 2.104.0 (from 2.100.0).
- Mobile build tools — Fastlane 2.241.2 (from 2.240.1) and CocoaPods 1.17.0, both under rbenv Ruby 4.0.9 with bundler 4.0.20, along with xcodeproj 1.28.1, xcpretty 0.4.1 and simctl 1.6.10.
- Node.js packages — TypeScript 7.0.2, pnpm 12.21.0 (from 12.4.2), npm 11.20.0, and eslint 10.15.0.
- Android SDK — Emulator 37.2.13 (from 37.1.11), Platform-Tools 37.0.1, Build-Tools 34 & 35, NDK 27, and SDK Manager 12.0.
- Google Chrome 157.0.8103.79 with a matching ChromeDriver 157.0.8103.78, at
/usr/local/bin/chromedriverwithCHROMEWEBDRIVERset to its directory. Chrome was at 153 on the previous build of this image. - Azure tooling —
azure-cliandbicepare now installed.
Ten Xcode Versions, One Label
Xcode 27.2 is selected by default. To build with any of the others, point DEVELOPER_DIR at it:
- name: Build with Xcode 27.0
env:
DEVELOPER_DIR: /Applications/Xcode_27.0.app/Contents/Developer
run: xcodebuild -version
Short names resolve to the installed build, so /Applications/Xcode_27.0.app works without knowing the patch version.
This is the widest toolchain range we have put in a single image. If you maintain a library that supports several Xcode generations, you can now test the whole support window on one runner label with a matrix:
jobs:
build:
runs-on: getmac-tahoe-rc
strategy:
matrix:
xcode: ["27.2", "27.0", "26.6", "26.1"]
env:
DEVELOPER_DIR: /Applications/Xcode_${{ matrix.xcode }}.app/Contents/Developer
steps:
- uses: actions/checkout@v4
- run: xcodebuild -version
The Metal Toolchain Is Already Installed
From Xcode 26, Apple stopped bundling the Metal compiler with Xcode and ships it as a separately downloadable component. On a stock runner that means the first xcrun metal in your build spends roughly 839 MB and several minutes fetching the toolchain from Apple before it compiles a single shader. Because the download comes from Apple's servers rather than ours, no build cache — ours or anyone's — can serve it for you.
On this image the toolchain is already mounted for every Xcode 26+ version, so a shader build starts compiling immediately:
| Xcode | Metal compiler |
|---|---|
| 27.2 | 32023.922 |
| 27.1 | 32023.921 |
| 27.0 | 32023.921 |
| 26.6 | 32023.883 |
| 26.5 | 32023.883 |
| 26.4.1 | 32023.883 |
| 26.3 | 32023.864 |
| 26.2 | 32023.864 |
| 26.1 | 32023.830 |
| 16.4 | 32023.620 |
Xcode 16.4 bundles its own Metal compiler inside the app, as every Xcode before 26 did. The nine newer versions get the separately shipped toolchain, pre-mounted.
If your project builds .metal files, or depends on anything that does — SceneKit, RealityKit, MetalFX, most game engines, a surprising number of image-processing packages — this is the difference between a job that compiles shaders and a job that downloads a compiler first.
Simulator Runtimes
Every platform now reaches 27.2:
| Platform | Runtimes |
|---|---|
| iOS | 27.2, 27.1, 27.0, 26.5, 26.4, 26.3, 26.1, 18.6 |
| tvOS | 27.2, 27.0, 26.5, 26.4, 26.2, 26.1, 18.5 |
| watchOS | 27.2, 27.0, 26.5, 26.4, 26.2, 26.1, 11.5 |
| visionOS | 27.2, 27.0, 26.5, 26.4, 26.2, 26.1, 2.5 |
There is no 27.1 runtime for tvOS, watchOS or visionOS — those platforms go 27.0 then 27.2. A destination pinned to OS=27.1 on them will not resolve.
Check Before You Switch
- Your default Xcode has moved from 27.0 to 27.2. Jobs on this label that don't set
DEVELOPER_DIRor runxcode-selectwere building with Xcode 27.0 and will now build with 27.2. To stay where you were, setDEVELOPER_DIR: /Applications/Xcode_27.0.app/Contents/Developer— 27.0 is still installed. - This is a Release Candidate label. Xcode 27.2 is a pre-release toolchain. Run your full build and test suite here before you rely on it, and keep release builds on a stable label.
- Two iOS 27.2 simulator runtimes are installed. One is the general runtime (24B8117); the other is a device-specific variant Apple ships for a single hardware model (24B91016s) and that rejects every other device. If a
simctl createor anxcodebuild -destinationstarts answeringIncompatible device, you have landed on the device-specific one — select the runtime explicitly rather than taking the newest. The same applied to iOS 27.1 and the iPhone Duo. - CocoaPods and Fastlane come from rbenv Ruby, not Homebrew.
cocoapodsis no longer a Homebrew formula on this image;podandfastlaneresolve through the rbenv shims on thePATH. Scripts that hard-code/opt/homebrew/bin/podneed updating to use the shim. - The pre-installed
pip3packages are leaner. The Python on thePATHshipspip,setuptools,wheel,certifiandpackagingonly —cryptographyandpydanticare no longer pre-installed. Install what you need in the job, or pin it in a requirements file. azure-cliis now installed as a cask rather than a Homebrew formula. Theazcommand is unchanged.- Docker and Colima are not installed, as on our other images.
- Major version bumps. Java 27, Rust 1.100 and Ruby 4.0 are all new generations relative to our current stable image.
- Keep the Xcode version in your cache keys. A DerivedData or module cache saved under Xcode 27.0 will still restore under 27.2, report a hit, and then be largely rebuilt anyway.
The 19 November Label Move Is Unchanged
As announced last week, on Thursday 19 November at 12:00 UTC three of our labels start pointing at a newer image. That move is unaffected by today's release:
| Label | Today | From 19 November |
|---|---|---|
getmac, getmac-latest, getmac-tahoe | Tahoe 26.5.2 · Xcode 26.6 | Tahoe 26.6.2 · Xcode 27.0 (default), 27.1 |
getmac-tahoe-rc | Tahoe 26.6.2 · Xcode 27.2 (default) + nine more | unchanged |
getmac-golden-gate-rc | macOS 27.2 · Xcode 27.2 | unchanged |
getmac-tahoe-legacy | Tahoe 26.3.2 · Xcode 26.4 | Tahoe 26.5.2 · Xcode 26.6 |
getmac-sequoia | Sequoia 15.6.1 · Xcode 16.4 | unchanged |
Our stable labels still default to Xcode 27.0 after the 19th. Xcode 27.2 stays on the two RC labels until it has run there long enough for us to promote it.
macOS Tahoe 26.3.2 with Xcode 26.4 is still retired on the 19th. getmac-tahoe-legacy is the only label that reaches it, and once that label moves to 26.5.2, nothing points at it. If you are pinned to Xcode 26.4 for a reason, tell us before then and we will work out where to put you.
GitHub Actions Integration
Use the following labels in your runs-on field:
getmac,getmac-latest, orgetmac-tahoe— macOS Tahoe 26.5.2 with Xcode 26.6 (current stable)getmac-tahoe-rc— macOS Tahoe 26.6.2 with Xcode 27.2 and nine earlier Xcode versions (Release Candidate)getmac-golden-gate-rc— macOS 27.2 Golden Gate with Xcode 27.2 (Release Candidate)getmac-tahoe-legacy— macOS Tahoe 26.3.2 with Xcode 26.4getmac-sequoia— macOS Sequoia 15.6.1 with Xcode 16.4
- runs-on: getmac-tahoe+ runs-on: getmac-tahoe-rcTo validate against Xcode 27.2 without giving up your stable builds, run both side by side with a matrix:
jobs:
build:
strategy:
matrix:
runner: [getmac, getmac-tahoe-rc]
runs-on: ${{ matrix.runner }}
For the full list of available labels, see our Workflow Labels documentation. For a complete breakdown of pre-installed tools, simulators, and SDKs, see the Installed Tools & Libraries page.
Get Started
The image is live now. Point a job at getmac-tahoe-rc to build and test against Xcode 27.2, or set DEVELOPER_DIR to reach any of the other nine toolchains.
As always, we'd love to hear your feedback — join our Discord community to share thoughts or request new tools.
— The GetMac Team