chore: Upgrade Xcode CI to 26.5#3953
Closed
mrousavy wants to merge 1 commit into
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
a599782 to
1ec488c
Compare
Owner
Author
|
Superseded by #3959. |
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
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
SWIFT_VERSION = 5.0; the Swift compiler comes from the selected Xcode, while a Swift 6 language-mode migration is a separate source-compatibility changeSource
/Applications/Xcode_26.5.appand iOS/macOS SDK 26.5: https://github.com/actions/runner-images/blob/main/images/macos/macos-26-Readme.mdValidation
ruby -e 'require "yaml"; ARGV.each { |f| YAML.load_file(f); puts "#{f}: ok" }' .github/workflows/build-ios-release.yml .github/workflows/harness-aws-device.yml\n-git diff --check\n- local machine is Xcode 26.3 / iOS SDK 26.2, so the actual Xcode 26.5 build must run in CI\n\n## Notes\nHarness tests are allowed to remain red per repo-owner guidance; release build workflow syntax is the relevant check for this PR.