CodeQL changes for macOS 27, Xcode 27, and Swift 6.4
Summary
Starting with macOS 27 and Xcode 27, Apple no longer includes Intel (x86_64) code in some of the system binaries and libraries that CodeQL relies on to trace builds. As… The post CodeQL changes for macOS 27, Xcode 27, and Swift 6.4 appeared first on The GitHub Blog .
Original Text
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> Starting with macOS 27 and Xcode 27, Apple no longer includes Intel (x86_64) code in some of the system binaries and libraries that CodeQL relies on to trace builds. As a result, CodeQL can’t support traced scans on these versions or analyze Swift 6.4.
What’s affected
Xcode 27: When Xcode 27 is installed, traced extraction isn’t available for C/C++, C#, Go, Java, Kotlin, or Swift.
macOS 27: Traced extraction may not be available for the previously mentioned languages.
Swift 6.4: CodeQL doesn’t support Swift 6.4 on any platform.
Intel-based Macs: CodeQL support for Intel-based Macs will be deprecated in mid-December 2026.
How to keep your scans running
If you scan Swift or use traced builds for other languages, pin your workflows to macOS 26 or earlier and Xcode 26 or earlier. If you use GitHub Actions, pin the runner image and toolchain in your workflow rather than relying on the latest versions.
For C/C++, C#, and Java, you can switch to build mode none, which doesn’t require tracing a build.
Join the discussion within GitHub Community.
The post CodeQL changes for macOS 27, Xcode 27, and Swift 6.4 appeared first on The GitHub Blog.
Lotu Radar provides attributed news summaries and links to the original publisher. Full reporting and copyright remain with the source.