Closed cpu closed 8 months ago
Would this include a release of futures-rustls as well? I think it has an identical changelist, although it was all done in one PR. One advantage of #58 is that releases could be synchronized in a workspace repo
Would this include a release of futures-rustls as well?
Sure, I can prepare a release over there as well :+1:
I think we should just do GitHub releases like we do in the other crates.
I agree, but I can't commit to creating releases for each of the previous tags this evening. I would be open to creating a new one for 0.26.0 if folks are interested in that.
I'd probably list the 0.23 upgrade first, seems like the most important part? Also maybe coalesce all the crypto provider stuff in a single bullet? It's really mostly aligning with upstream and not actually much of a change for this crate IMO.
SGTM. Updated!
I agree, but I can't commit to creating releases for each of the previous tags this evening. I would be open to creating a new one for 0.26.0 if folks are interested in that.
No, I just meant for this one.
Thank you!
Published tokio-rustls v0.26.0 at registry crates-io
, published a release at https://github.com/rustls/tokio-rustls/releases/tag/v%2F0.26.0.
Preparation to cut a new 0.26.0 release to bring in changes since 0.25.
This repo doesn't have an established CHANGELOG or GitHub releases, but the major callouts I would include would be:
Additions
fips
feature - by @BiagioFesta in #43, @jbr in #49, #50Fixes
NotConnected
error inpoll_shutdown
- by @djc in #42ErrorKind::WouldBlock
inMidHandshake::SendAlert
poll - by @jbr in #47ErrorKind::WouldBlock
inLayzConfigAcceptor
- by @jbr in #48SendAlert
io::ErrorKind
- by @jbr in #52alert.write
poll - by @jbr in #51