-
Notifications
You must be signed in to change notification settings - Fork 10.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Xcode version check more lenient #61561
Merged
swift-ci
merged 1 commit into
swiftlang:main
from
keith:ks/make-xcode-version-check-more-lenient
Nov 2, 2022
Merged
Make Xcode version check more lenient #61561
swift-ci
merged 1 commit into
swiftlang:main
from
keith:ks/make-xcode-version-check-more-lenient
Nov 2, 2022
Conversation
This file contains 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
kastiglione
reviewed
Oct 12, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems like a reasonable approach.
keith
force-pushed
the
ks/make-xcode-version-check-more-lenient
branch
from
October 12, 2022 23:46
e1c6693
to
969cbeb
Compare
@swift-ci please smoke test |
keith
force-pushed
the
ks/make-xcode-version-check-more-lenient
branch
from
November 2, 2022 00:06
e3f7070
to
17aba8a
Compare
@swift-ci please smoke test and merge |
This allows any versions above a specific version, instead of requiring a specific list. Since it seems like many folks just disable this check entirely, this list definitely isn't kept up well. If we need to exclude a specific version, like if 1 Xcode beta didn't support it but the next did, we can add a new list using the old method to validate build numbers and disallow the bad version(s). I don't recall why we didn't do this over a list originally, nor can I find any context on why in the original discussion swiftlang#34227
keith
force-pushed
the
ks/make-xcode-version-check-more-lenient
branch
from
November 2, 2022 03:36
17aba8a
to
6a32e91
Compare
@swift-ci please smoke test and merge |
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.
This allows any versions above a specific version, instead of requiring a specific list. Since it seems like many folks just disable this check entirely, this list definitely isn't kept up well. If we need to exclude a specific version, like if 1 Xcode beta didn't support it but the next did, we can add a new list using the old method to validate build numbers and disallow the bad version(s).
I don't recall why we didn't do this over a list originally, nor can I find any context on why in the original discussion #34227