Widen pin on swift-crypto dependency#332
Merged
gwynne merged 5 commits intovapor:mainfrom Feb 18, 2026
Merged
Conversation
gwynne
approved these changes
Feb 18, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #332 +/- ##
==========================================
- Coverage 68.37% 68.22% -0.15%
==========================================
Files 9 9
Lines 332 321 -11
==========================================
- Hits 227 219 -8
+ Misses 105 102 -3 🚀 New features to boost your workflow:
|
Member
|
Github Actions is freaking out, forcing the merge anyway |
Contributor
Author
|
thanks @gwynne |
This file contains hidden or 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
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.
These changes are now available in 4.10.1
What?
Widens the supported
swift-cryptorange to include the 4+ series of releases.Why?
swift-crypto4.2.0 doesn't seem to impact the building or testsswift-crypto4+ tags to still use this librarymysql-niowidening its pin onswift-cryptowould allowvaporusers depending onfluent-mysql-driverto use the latest, and safest,swift-cryptoversions.Related to
vapor/mysql-nio#120