Skip to content

Conversation

@madrob
Copy link
Contributor

@madrob madrob commented Nov 13, 2025

Xcode-latest currently points to the 26.1 release so it gives us a false sense of version coverage, and should be ignored.

Motivation:

We do not need to build twice with the same environment.

Modifications:

Set default value for Xcode latest beta enabled to false

Result:

One fewer job generated for the macOS build matrix.

Xcode-latest currently points to the 26.1 release so it gives us a
false sense of version coverage, and should be ignored.
@madrob madrob requested a review from rnro November 13, 2025 17:22
@madrob madrob added the semver/none No version bump required. label Nov 13, 2025
@madrob
Copy link
Contributor Author

madrob commented Nov 13, 2025

I'm not sure why the matrix still generated a job for Xcode-latest here. Is it explicitly using the version committed to the base branch instead of the version I have in the PR?

https://github.com/apple/swift-nio/actions/runs/19340051165/job/55325750250?pr=3446

@rnro
Copy link
Contributor

rnro commented Nov 17, 2025

I'm not sure why the matrix still generated a job for Xcode-latest here. Is it explicitly using the version committed to the base branch instead of the version I have in the PR?

https://github.com/apple/swift-nio/actions/runs/19340051165/job/55325750250?pr=3446

We reference branch main in all our workflows so you need to push a commit redirecting the workflows to use your branch if you want to test it then back it out before merging. In this case I don't think that's necessary.

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.

2 participants