Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
mrousavy
added this pull request to stack #1817
October 19, 2026 22:04
This branch was successfully deployed
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.
iOS validation stops during package resolution because V1 requires Swift 6.4 and the macOS 26 runner provides Swift 6.3.3.
Use the
xcode-27runner and Xcode 27.1 for iOS builds, runtime tests, release validation and lockfile updates. Select the installed iOS 27 simulator for standalone tests and Harness. Existing Xcode-based cache keys pick up the new toolchain.Verified the runner's installed tools and simulators against actions/runner-images. All six workflow files parse, actionlint passes with the preview label registered in its configuration, and
git diff --checkpasses. The iOS Release build passed with this toolchain. Existing runtime assertion failures are handled in #1808 and #1809.