You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updates krates to 0.16.10 to fix a bug originally filed on this repo,
EmbarkStudios/krates#82. This bug meant that
depending on the same crate multiple times by using different ``cfg()`
expressions could cause crates that were pulled in by features to not be
properly appended to the graph, and thus not checked by cargo-deny.
Describe the bug
When an optional feature is added depending on a
cfg
, the dependencies it brings in are not scanned by cargo deny. I expected that would be the case.To reproduce
cargo deny check ban
deny.toml
Cargo.toml
cargo-deny version
0.14.20
What OS were you running cargo-deny on?
Linux
Additional context
If we remove the main dependencies, the banned crate its detected as expected
Cargo.toml
I try to play with the resolver and tweaking cargo-deny options without success
The text was updated successfully, but these errors were encountered: