I would have guessed that cargo would do this automatically, but for some reason tide-rustls was continuing to pull in 0.18 even after a cargo update and rebuilding cargo.lock
This is because because both 0.18 and 0.19 are getting pulled in, somehow having to do with optional features. I'll close this PR because I don't know how to fix the underlying cargo problem.
I would have guessed that cargo would do this automatically, but for some reason tide-rustls was continuing to pull in 0.18 even after a cargo update and rebuilding cargo.lock