Not finding outdated libraries

[VorpalBlade]

$ cargo outdated -w
All dependencies are up to date, yay!
$ cargo update
    Updating crates.io index
    Updating core-foundation-sys v0.8.3 -> v0.8.4
    Updating enumflags2 v0.7.5 -> v0.7.6
    Updating enumflags2_derive v0.7.4 -> v0.7.6
    Updating futures-core v0.3.27 -> v0.3.28
    Updating futures-io v0.3.27 -> v0.3.28
    Updating futures-macro v0.3.27 -> v0.3.28
    Updating futures-sink v0.3.27 -> v0.3.28
    Updating futures-task v0.3.27 -> v0.3.28
    Updating futures-util v0.3.27 -> v0.3.28
    Updating linux-raw-sys v0.3.0 -> v0.3.1
    Updating proc-macro2 v1.0.54 -> v1.0.56
    Updating rustix v0.37.4 -> v0.37.6
    Updating syn v2.0.11 -> v2.0.13
$ cargo outdated --version
cargo-outdated 0.11.2

Clearly something isn't quite right here. I'm using sparse registry by the way, if that causes any issues.

[nathanfranke]

Perhaps I'm missing something but cargo outdated seems not to detect a basic outdated dependency. It said all dependencies are up to date, so to test I changed the version of chrono from 0.4.26 to 0.4.25, then ran cargo run to make sure cargo is aware. Running cargo outdated again still shows all dependencies are up to date.

Using cargo-outdated 0.11.2 (I also skipped most of the installation instructions like PATH, shouldn't be necessary if cargo already works right? Could be my fault, but also likely could be improvements here).

[w-flo]

so to test I changed the version of chrono from 0.4.26 to 0.4.25

To clarify: Did you change the version by specifying "0.4.25" in Cargo.toml? If so, cargo will automatically pick the latest 0.4.x version (i.e. 0.4.26). Changes in the "patch" version number are assumed to be backwards-compatible.

Generally speaking though, it looks like cargo-outdated needs an update to be compatible with cargo's recent switch to sparse registry. That's PR #346.