fix(ci): pin client SDK macOS jobs to macos-15 for Xcode 16.2#302
Merged
Conversation
The macos-latest runner label is migrating to macOS 26 (started June 15, 2026), which no longer ships Xcode 16.2. Jobs landing on the new image fail at the xcode-select step (sudo xcode-select -switch /Applications/Xcode_16.2.app), while jobs on the old macOS 15 image still pass — making CI a coin flip. Bump the pinned Xcode version to 26.3 rather than pinning the runner to the soon-to-be-deprecated macos-15. 26.3 is present on both the current macOS 15 and the new macOS 26 images, so it works regardless of which image a run lands on during the migration window. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mattrmc1
force-pushed
the
mmccarthy/fix/ci-pin-macos-15
branch
from
d49325b to
ddd3ed9
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit ddd3ed9. Configure here.
tanderson-ld
approved these changes
Jun 30, 2026
Revert the Xcode 26.3 bump in favor of pinning the runner. The macos-latest migration to macOS 26 dropped both Xcode 16.2 AND Android SDK platform API 34, so bumping only Xcode still fails when the net8.0-android target builds (android-34 is absent on macOS 26). macos-15 carries both Xcode 16.2 and Android API 34, fixing CI in a single change without altering what is built. Migrating the client SDK to the macOS 26 toolchain (Xcode 26 + Android API 35) should be done deliberately in a separate PR. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
tanderson-ld
approved these changes
Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
macos-latestrunner label is migrating to macOS 26 (started June 15, 2026), which does not ship Xcode 16.2. The client SDK build requires Xcode for its iOS workloads and pinsxcode-version: '16.2'via the./.github/actions/xcode-selectaction.Jobs that land on the new macOS 26 image fail immediately at the xcode-select step, since
/Applications/Xcode_16.2.appdoes not exist there:Jobs that still land on macOS 15 pass, so CI is currently nondeterministic — the same commit
a03e942produced both a passing and a failingbuild-and-test (macos-latest)run, and the failing run carries GitHub's own migration notice annotation.This pins the macOS jobs to
macos-15, where Xcode 16.2 remains installed, so the existingxcode-version: '16.2'pin stays valid:sdk-client-ci.yml—build-and-testmatrixrelease-sdk-client.yml—buildandpublishjobsNotes
macos-15is itself a temporary target and will eventually be deprecated. The longer-term follow-up is validating the iOS build against Xcode 26 on the macOS 26 image; this change is the minimal hotfix to keep CI and releases green in the meantime.Testing
CI on this branch runs the client SDK
build-and-testjob onmacos-15and completes the xcode-select step successfully.Note
Low Risk
CI/release runner label change only; no application code or secrets handling changes.
Overview
Pins client SDK GitHub Actions jobs from
macos-latesttomacos-15so they stay on an image that still has Xcode 16.2, matching the existing./.github/actions/xcode-selectpin.sdk-client-ci.yml—build-and-testmatrix OS label.release-sdk-client.yml—buildandpublishjobruns-onvalues. This avoids nondeterministic failures whenmacos-latestmoves to macOS 26, where/Applications/Xcode_16.2.appis missing and the xcode-select step fails immediately.Reviewed by Cursor Bugbot for commit 21e3497. Bugbot is set up for automated code reviews on this repo. Configure here.