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
If a project's dependency tree contains two different versions of the same package1, cargo-lichking mostly does the right thing and handles them separately (though the list command's output could be improved in this situation), but when it comes to the split variant of bundle, only one file will be created for such a package, and there's no indication which version of the package it's for.
Footnotes
This is a thing that can happen if the versions are not semver compatible. For example, if you add both serde 1.0.190 (which indirectly depends on syn 2.0) and derive-more 0.99.17 (which depends on syn 1.0.3), you'll end up with both syn 1.x and syn 2.x in your dependency tree. ↩
The text was updated successfully, but these errors were encountered:
If a project's dependency tree contains two different versions of the same package1,
cargo-lichking
mostly does the right thing and handles them separately (though thelist
command's output could be improved in this situation), but when it comes to thesplit
variant ofbundle
, only one file will be created for such a package, and there's no indication which version of the package it's for.Footnotes
This is a thing that can happen if the versions are not semver compatible. For example, if you add both serde 1.0.190 (which indirectly depends on syn 2.0) and derive-more 0.99.17 (which depends on syn 1.0.3), you'll end up with both syn 1.x and syn 2.x in your dependency tree. ↩
The text was updated successfully, but these errors were encountered: