To make a long story short, I updated a
bytes dependency from 0.5 to 0.6 in a library crate, and I got build errors further down the dependency tree, which rust hinted might be due to multiple versions being pulled in, and indeed
tokio-test still pulls in 0.5.
I thought that the idea was that 0.6.X should be backwards compatible with 0.5.X? Or is special because major version is 0? Is tokio-test forcing 0.5 in some manner?