Repository navigation
build: raise macOS deployment target to 12.0 - #126
Merged
Merged
Conversation
Xcode 27 refuses to build the project: its supported deployment target range starts at 12.0, while the app target was pinned to 11.5 and the test target to 11.0. Both values predate this release; they were last valid under the Xcode that shipped 2.3.9. This drops support for macOS 11 Big Sur, so it is a user-visible change and belongs in the 2.4.0 release notes. CI stays pinned to Xcode 26.6: Xcode 27 is not installed on the macos-26 runner image, and is only reachable through the separate xcode-27 image label that GitHub currently marks as preview. A 12.0 target builds on 26.6, so the gate remains valid. Verified on Xcode 27.0 (27A266a): Debug test run 46/46 passing, Release configuration builds.
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
1 participant
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.
Xcode 27 refuses to build this project at all: its supported deployment target range starts at 12.0, and the app target is pinned to 11.5 with the test target at 11.0. It is a hard error before compilation, not a warning. Both values predate the 2.4.0 work; they were last valid under the Xcode that shipped 2.3.9.
Merging drops macOS 11 Big Sur. That is the decision worth a second opinion here, and it is the reason this is a separate commit rather than part of the release: the minimum OS is a product call, not a build detail, and it needs a line in the 2.4.0 notes.
CI stays on Xcode 26.6. Repointing it at Xcode 27 to match the local toolchain does not work: Xcode 27 is not installed on the macos-26 runner image, which tops out at 26.6, and is only reachable through a separate
xcode-27image label that GitHub marks as preview and warns is unstable. A 12.0 target builds cleanly on 26.6, so the gate still covers the change; the cost is that CI no longer matches whatever Xcode the release is archived on.The 10.9 values left in the project-level configurations are untouched. Both targets override them, so they never apply, and folding that cleanup in here would blur what this commit is for.