feat: Swift 6 support and switch to swift-testing #283
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
b50f06d to
d8837f8
Compare
6223151 to
755147f
Compare
e98b388 to
562bdff
Compare
I dropped old deprecation warnings as this is definitely a major version bump. For Swift 6 support, some of the types that were sent with errors are now wrapped in a "sendable" variety so that they're async safe. The GitHub builds also heavily use matrix support for multiple platform builds now, too.
562bdff to
eb46122
Compare
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.
At least relates to #281.
The bulk of this work is actually switching to swift-testing.
Questions to consider (this list may grow):
matrixbuild and specify the image that has Swift 6 in it... pretty easy.maxim-lobanov/setup-xcode@v1XMLElementSendable... but it has to have a name