Skip to content
Brief Innovation & Growth ·

CodeQL loses traced scans with Xcode 27 and skips Swift 6.4

GitHub says Apple's removal of Intel code breaks traced scans with Xcode 27 and may break them on macOS 27.

In brief
  • GitHub says CodeQL cannot analyze Swift 6.4 on any platform. Traced scans are unavailable with Xcode 27 and may be unavailable on macOS 27.
  • GitHub points C/C++, C#, and Java teams to build mode none. Teams that need traced scans or scan Swift should stay on macOS 26 or Xcode 26 or older.

GitHub said on 19 October 2026 that CodeQL, its code-scanning tool, is changing for Apple's next releases. Apple no longer ships Intel (x86_64) code in some system files CodeQL uses to trace builds, GitHub said. Tracing means watching a real build run to see what it compiles. CodeQL also cannot analyze Swift 6.4 on any platform. GitHub will deprecate Intel Mac support in mid-December 2026.

GitHub says traced extraction is unavailable for C/C++, C#, Go, Java, Kotlin and Swift once Xcode 27 is installed. On macOS 27 it may be unavailable for those languages. GitHub advises teams that scan Swift or use traced builds to stay on macOS 26 or Xcode 26 or older. In GitHub Actions, it says to name exact versions instead of taking the latest. For C/C++, C#, and Java, GitHub points to build mode none, which needs no traced build. GitHub does not say what coverage that mode changes, or when support might return.

This part is interpretation, not GitHub's claim. Swift 6.4 code cannot be scanned at all, so teams that keep scanning must hold back their own toolchain upgrades. The pinned version then becomes a security dependency. Teams can check whether a skipped or failed scan would show up in their reports.

A WebPulse Brief: a short report of an important event, written by the WebPulse Newsroom with AI assistance and checked against the reporting below. When there is more to explain, we follow up with a full story. How we use AI.

Reporting: GitHub.