Cargo-edit: cargo upgrade or cargo check-updates - upgrade dependencies to the latest versions, regardless of existing version constraints

[887]

Similar to this, only for cargo:
https://github.com/tjunnone/npm-check-updates

Maybe this feature already exists but i couldn't find it, and nobody at the last meet knew about it.

[killercup]

Sounds like an automated cargo outdated + editing Cargo.toml.

Could also work as a fork of cargo update.

Am 07.02.2016 um 11:23 schrieb 887 [email protected]:

Similar to this, only for cargo:
https://githubcom/tjunnone/npm-check-updates

Maybe this feature already exists but i couldn't find it, and nobody at the last meet knew about it

—
Reply to this email directly or view it on GitHub.

[robinst]

For anyone landing here from a search, cargo-outdated (install via cargo install cargo-outdated) already works for printing the versions: cargo outdated

[bjgill]

Given that cargo-list is on the way to deprecation, I think the correct way to do this would be to use cargo as a library to parse the manifest. We could then plug this into the existing cargo add --update-only to get something that was a good approximation to a proper cargo upgrade.

There'd then be additional work to properly support workspaces, implement some sort of 'check mode' and handle all the possible variations of dependency (dev/build/optional/etc.).

@killercup - I'd hope to get an MVP done within the next fortnight. Would that work with your plan for v0.2?