Use updated dependencies when building with Swift 5, but keep backwards-compatibility with Swift 4 #2999
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 is a complement to #2972, but doesn't make any breaking changes to CI / homebrew. It starts the work of upgrading to Swift 5.2 by using updated dependencies when Carthage is built with a 5.x compiler. These changes are helpful for users who depend on Carthage as a SwiftPM package [1], and should make it a little easier to drop support for Swift 4.x in the future.
[1]: Carthage doesn't build with Commandant >= 0.17.0, because that version drops support for antitypical/Result. You can manually pin Commandant to an older version, but then you can't depend on tools that have upgraded to the newer version of Commandant, like SwiftLint. So this PR helps keep users out of dependency hell when they're using SwiftPM to version their build tools.