Cargo outdated vs plain cargo

help
1

Revisiting this, I contacted the cargo-outdated developer/maintainer and asked if it is still being developed/maintained, and if there's any chance the problems with private registries could be fixed.

They replied that cargo is getting more and more native support for what cargo-outdated does, so there's less incentive to do a lot of work on it -- which I can understand. (Looking at the commit logs, it does get fixes though).

I've noticed that when I run cargo update, and it updates a dependency, it will note that there's a newer incompatible version:

  Updating embed-resource v2.4.3 -> v2.5.1 (available: v3.0.2)

This is basically the information I want from cargo-outdated. However, once it has made the "minor" update (2.4.3 to 2.5.1 update in this case), it won't output the "available" version next cargo update run.

What cargo subcommand/options can one run to get a list of crates that have new (incompatible) versions without needing it to do a minor upgrade in the process?

2

Does cargo update --verbose give you what you want?

1 Like
3

I think it does -- thank you!

I wish there was something akin to cargo-outdated's --depth=1, but at this point I'm just happy to get the functionality at all for private registries, so I'm not going to complain. :slight_smile: