Closed jplatte closed 1 year ago
I'd rather have specific exceptions than accepting all duplicate dependencies
I'm okay either way 😅
I'd rather have specific exceptions than accepting all duplicate dependencies
The problem with this, as mentioned in the commit message, is that CI frequently breaks from it from dependencies just doing their regular maintenance and upgrading dependencies. I also like avoiding duplicate dependencies, very much (recently went to upgrade syn in a bunch of places that hadn't upgraded to 2.0 yet). But more often than not, it's non-trivial to fix these and unrelated contributions get stuck on it, especially when the project isn't receiving frequent updates (like tower-http, currently).
Fair enough
Motivation
CI is failing in other PRs, with no fault of the PR authors.
Solution
Stop erroring on duplicate dependencies in the
cargo-deny
check.