Skip to content

Conversation

@rnro
Copy link
Contributor

@rnro rnro commented Jun 12, 2025

Add Xcode 26 beta 1 to macOS CI and disable Xcode 16.1 jobs by default

Motivation:

  • Xcode 26 beta 1 is now released, we should test our code on it.
  • We should drop 16.1 to conserve the number of jobs. 16.1 isn't offering much coverage anyway since it has the same Swift minor version (6.0) as Xcode 16.2.

Modifications:

  • Enable use of Xcode 26 beta 1 by default.
  • Disable Xcode 16.1 jobs by default

Result:

  • This and downstream repos will run Xcode builds on Xcode 26 beta 1.
  • Xcode 16.1 jobs won't run by default on this or downstream repos but will run if explicitly requested.

An example of this working https://github.com/apple/swift-nio/actions/runs/15614383580/job/43983277904?pr=3267

rnro added 3 commits June 12, 2025 15:57
Motivation:

Xcode 26 beta 1 is now released, we should test our code on it.

Modifications:

Enable use of Xcode 26 beta 1 by default.

Result:

This and downstream repos will run Xcode builds on Xcode 26 beta 1.
Motivation:

Now that we're adding Xcode 26 beta 1 support we should drop 16.1 to
conserve the number of jobs. 16.1 isn't offering much coverage anyway
since it has the same Swift minor version (6.0) as Xcode 16.2.

Modifications:

Disable Xcode 16.1 jobs by default

Result:

Xcode 16.1 jobs won't run by default on this or downstream repos but will
run if explicitly requested.
@rnro rnro added the semver/none No version bump required. label Jun 12, 2025
@rnro rnro marked this pull request as ready for review June 12, 2025 15:21
This reverts commit 31992aa.
@rnro rnro enabled auto-merge (squash) June 12, 2025 15:23
@rnro rnro merged commit d24d9ab into main Jun 12, 2025
36 of 41 checks passed
@rnro rnro deleted the add_xcode_26_b1_to_macos_ci branch June 12, 2025 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver/none No version bump required.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants