Cargo: 0.25.0 -> 0.26.0

[cpu]

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

• Support for Rustls 0.23 and the new acceptor alert API - by @ctz in Take rustls 0.23 #44
• Support for aws-lc-rs as the new default crypto backend, allowing passthrough of the fips feature - by @BiagioFesta in Cargo.toml: add aws-lc-rs feature as crypto backend #43, @jbr in feat: add fips pass-through feature #49, feat: change default crypto provider to match rustls' #50
• Support for forwarding vectored writes - by @paolobarbolini in Forward vectored writes #45

Fixes

• Ignoring NotConnected error in poll_shutdown - by @djc in Ignore NotConnected error in poll_shutdown() #42
• Check for ErrorKind::WouldBlock in MidHandshake::SendAlert poll - by @jbr in fix: check for ErrorKind::WouldBlock in MidHandshake::SendAlert poll #47
• Check for ErrorKind::WouldBlock in LayzConfigAcceptor - by @jbr in Fix: Check for ErrorKind::WouldBlock in LazyConfigAcceptor #48
• Fix for SendAlert io::ErrorKind - by @jbr in fix: correctly poll alert.write until it finishes #52
• Fix for alert.write poll - by @jbr in Fix: SendAlert io::ErrorKind should be InvalidData instead of Other #51

[jbr]

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

[cpu]

Would this include a release of futures-rustls as well?

Sure, I can prepare a release over there as well 👍

Edit: rustls/futures-rustls#11

[djc]

Makes sense to me! I think we should just do GitHub releases like we do in the other crates. 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.

[cpu]

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!

[djc]

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.

[quininer]

Thank you!

[djc]

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.