Widen swift-crypto version range #8680
Open
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.
.upToNextMinor(from: "3.0.0")on swift-crypto prevents updating of dependent packages that need swift-crypto >= 3.1.0.Motivation:
We need to depend on SwiftPM (for reasons laid out here) and the narrow version range on swift-crypto (which is at version 3.12.3) prevents us from updating to a newer version of PostgresNIO, which requires swift-crypto >= 3.9.0.
Modifications:
This opens the range to 3.0.0 ..< 3.13.0, although perhaps simply
upToNextMajorwould also be acceptable? It would certainly prevent future instances of this happening.Result:
Dependents are able to update to the latest swift-crypto.