Closed briansmith closed 1 year ago
Also, I released 0.22.2 yesterday specifically so people could pin to 0.22.2 if they would rather have an unsupported version of ring than have 0.17.0 for some reason.
Merging #288 (9de8c5f) into main (e7873ff) will not change coverage. Report is 1 commits behind head on main. The diff coverage is
n/a
.
@@ Coverage Diff @@
## main #288 +/- ##
=======================================
Coverage 57.43% 57.43%
=======================================
Files 21 21
Lines 3597 3597
=======================================
Hits 2066 2066
Misses 1531 1531
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
@ctz @cpu Since webpki 0.22 needs to live a long time to support Rustls 0.20.x (and anything else?)
For what it's worth, I believe based on the Rustls SECURITY.md the 0.20.x release is no longer within the advertised support window.
@ctz @cpu Since webpki 0.22 needs to live a long time to support Rustls 0.20.x (and anything else?), I need to release a version that uses ring 0.17.0, since I don't want to keep supporting ring 0.16.x any longer than I need to.
However, I am going to hold off on the release for a little bit until more people have tested 0.17.0.