Apple shipped Xcode 27.2 RC, build 27B48, on October 19, alongside matching platform release candidates including iOS and iPadOS 27.2 RC (24B115) and macOS 27.2 RC (26B118). The build pairs with Swift 6.4. Buried in the release notes is a change with more teeth than a routine point update: a new .xcproj format that stores project data as JSON, positioned alongside the decades-old .xcodeproj format Xcode has used since its earliest versions.
For product and design leads running iOS or Mac shops, the stakes sit in tooling continuity, not features. A project file format is infrastructure. Build scripts, CI pipelines, linting tools, and merge workflows all parse .xcodeproj today, and many of those integrations assume its specific plist-like structure. Apple's notes describe .xcproj as a new, parallel format rather than a mandatory migration, but engineering leads need to confirm whether existing CI configs, third-party build tools, and git merge drivers handle the new format before adopting it on any shared branch.
Apple's announcement also lists Device Hub improvements and a tool called GetCodeCoverage, delivered over MCP, the protocol that lets external agents query structured data from a host application. The practical effect: a coding agent or automated workflow can now pull test coverage numbers directly out of Xcode rather than parsing exported reports by hand. What the release notes do not spell out is which MCP clients are supported out of the box or how coverage data is scoped across targets, details that matter for anyone building automated review or CI gating around it.
The mechanism worth watching is adoption pressure versus compatibility risk. Dual-format support usually means Apple intends .xcproj to eventually replace .xcodeproj, the way Swift Package Manager slowly displaced older dependency tools. JSON is easier to diff, easier to generate programmatically, and friendlier to tooling built by teams outside Apple's own IDE stack. That is the upside for design and build tooling leads who have long complained about merge conflicts in Xcode's existing project format. The downside is a transition window where some tools understand one format and not the other.
None of this is optional reading for release engineering. An RC, by definition, signals Apple expects to ship this build, or something very close to it, as the shipping version. Teams planning iOS 27.2 submissions should pull the RC now, not after general availability, because build-system changes tend to surface incompatibilities in CI before they surface in app behavior. Xcode 27.2 RC is the first place to confirm whether a pipeline tolerates .xcproj at all.
Apple's release notes do not say when .xcodeproj support ends, if ever. Until that date appears, treat .xcproj as additive, test it in an isolated branch, and keep .xcodeproj as the format of record for any pipeline that has not been explicitly rebuilt against build 27B48.