Xcode 26.1 Beta 1
Xcode 26.1 beta requires a Mac running macOS Sequoia 15.6 or later.
[…]
The ‘devicectl’ command line tool now supports gathering a sysdiagnose from a connected device. To use this functionality, run ‘xcrun devicectl device sysdiagnose’
[…]
When enabling Hardware Memory Tagging under Enhanced Security (Capabilities editor -> Enhanced Security -> Memory Safety -> Enable Hardware Memory Tagging), all applications will currently run under Soft Mode irrespective of the Soft Mode for Memory Tagging option.
[…]
Fixed: If an issue is recorded during a Swift Testing test via an API such as
#expectorIssue.record()in a context which is unassociated with the test, such as viaTask.detached { … }or aDispatchQueue, the test process no longer unexpectedly terminates and Xcode shows the issue.
Previously:
4 Comments RSS · Twitter · Mastodon
Honest question, as I migrated to macOS 15 (Apple named Sequoia, currently 15.6.1) last spring when forced to because of Xcode requirements....
Was the baseline for Xcode 26.0 this, or has it already changed? (I'm hoping to avoid upgrading to macOS 26.x until the next calendar year, if ever.)
@Dave The release version of Xcode 26 required macOS 15.6. Earlier betas worked on earlier versions.
@Dave if history is a guide, it will be the Feb/March 2026 update of Xcode that will drop macOS 15 support and require macOS 26.
They’ve been following that pattern consistently for many years now.
You can see it in the table at https://xcodereleases.com/
Support for older OSes doesn't just drop once they raise the minimum, and often, Xcode versions have worked fine in both directions (Apple also limits where older Xcode versions can launch normally). It just means they stop caring and they might use, somewhere, private or otherwise API, only available on the newer OS. In this case, since 26 is such a visual overhaul (for the worst, but still), it will be interesting to see how much they break once stop caring.
