`codeql-action/init` Makes Metal Toolchain Unavailable on macOS 26 Runners
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github-actions, macos, typescript
Research direction
Start with the reproduction workflow in the issue and compare xcrun metal -v before and after github/codeql-action/init@v4 on a macOS 26 runner. Read the init action entry point and inspect how initialization affects Xcode selection or Metal toolchain visibility. Done means the selected Xcode's Metal toolchain remains available and the shown checks and Metal-compiling build succeed.
Written by the indexing model from the issue text.
Description
Description
Swift/iOS builds fail after github/codeql-action/init with Xcode 26 on macOS 26 GitHub-hosted runners when the build needs the Metal toolchain.
The failing build error is:
error: error: cannot execute tool 'metal' due to missing Metal Toolchain; use: xcodebuild -downloadComponent MetalToolchain
Command CompileMetalFile failed with a nonzero exit code
This was originally discussed in actions/runner-images:
- Runner-images issue: https://github.com/actions/runner-images/issues/13014
- Maintainer repro:
xcrun metal -vworks after Xcode selection, then fails aftercodeql-action/init: https://github.com/actions/runner-images/issues/13014#issuecomment-4259404015 - See comment by @v-sergei-pyshnoi , pointing to an issue here: https://github.com/actions/runner-images/issues/13014#issuecomment-4303584735
Reproduction outline
jobs:
codeql-metal-repro:
runs-on: macos-26
permissions:
contents: read
security-events: write
steps:
- uses: actions/checkout@v4
- name: Select Xcode
uses: maxim-lobanov/setup-xcode@v1
with:
xcode-version: latest-stable
- name: Check Metal before CodeQL init
run: |
xcodebuild -version
xcrun --find metal
xcrun metal -v
- name: Initialize CodeQL
uses: github/codeql-action/init@v4
with:
languages: swift
build-mode: manual
- name: Check Metal after CodeQL init
run: |
xcrun --find metal
xcrun metal -v
- name: Build
run: |
# Run the normal xcodebuild command for an iOS app target that compiles Metal files.
xcodebuild ...
Expected: xcrun metal -v and the xcodebuild invocation continue to find the selected Xcode’s Metal toolchain after CodeQL initialization.
Actual: after codeql-action/init, xcrun metal -v / CompileMetalFile can fail with “missing Metal Toolchain”, even though the runner image appears to have the toolchain available before CodeQL initialization.
Note: Xcode 26 changed Metal Toolchain distribution/visibility, and MacPorts documented extra steps sometimes needed to make the toolchain visible to all users:
https://trac.macports.org/wiki/TahoeProblems#MetaltoolchainisnolongerbundledinXcode
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 493
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 44
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/codeql-action
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/codeql-action#4052 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
github/codeql-action#4078 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
github/codeql-action#4008 · 9 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
github/codeql-action#3915 · 6 comments · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
github/codeql-action#3870 · 3 comments · 1 reaction ·
All issues in github/codeql-action
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·