Show version requirements to determine cause for duplicates #762
Description
I'm trying to figure out if I can modify my dependency tree to avoid duplicates. I'm currently going over the packages in the emitted tree, looking up the source of the Cargo.toml of the version of that package to determine what it's version requirements are. I am looking for a better way to do this.
Could cargo-deny output the version restrictions imposed by the depending crate? Or could it create a link to the source file like https://docs.rs/crate/windows-registry/0.5.1/source/Cargo.toml?
Is there a better way to learn where the conflicting requirements are coming from?
I'm sure this has been asked before but I couldn't find the right search terms in the issue tracker and the discord invite has expired.