fix(ref): Clarify transition for reporting stale dependencies

This commit is contained in:
Ed Page 2024-02-02 10:46:21 -06:00
parent 3ee143a834
commit 064fdac8d5
1 changed files with 1 additions and 1 deletions

View File

@ -797,7 +797,7 @@ In addition to the `cargo update` output to report when things are held back (bo
We can attempt to have resolves to call out the new dependency versions that were held back from MSRV or semver.
Whether we do this and how much will be subject to factors like noisy output, performance, etc.
Implementation ideas...
Some approaches we can take for doing this include:
We then do a depth-first diff of the trees, stopping and reporting on the first different node.
This would let us report on any command that changes the way the tree is resolved