From 3ecc7a9b7d5ff6d668a383a9c0963b03c7804b0c Mon Sep 17 00:00:00 2001 From: "Michael B. Gale" Date: Fri, 30 Oct 2026 12:56:44 +0000 Subject: [PATCH] Add change note --- unreleased-change-notes/macos-xcode-deprecation.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 unreleased-change-notes/macos-xcode-deprecation.md diff --git a/unreleased-change-notes/macos-xcode-deprecation.md b/unreleased-change-notes/macos-xcode-deprecation.md new file mode 100644 index 000000000..ea7586d08 --- /dev/null +++ b/unreleased-change-notes/macos-xcode-deprecation.md @@ -0,0 +1 @@ +- Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See [this blog post for more information](https://github.blog/changelog/2026-10-19-codeql-changes-for-macos-27-xcode-27-and-swift-6-4/). The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the [Tool Status Page](https://docs.github.com/en/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/use-the-tools-status-page-for-code-scanning). This check will be rolled out following this release of the CodeQL Action. [#4221](https://github.com/github/codeql-action/pull/4221)