Skip to content

Trouble updating library usage from v0.9: replacement for LocalManifest::upgrade? #837

@tarcieri

Description

@tarcieri

cargo-audit uses cargo-edit as a library as part of its --fix functionality in order to attempt to automatically update Cargo.lock with versions containing fixes.

We're currently on cargo-edit v0.9 using LocalManifest::upgrade to perform the upgrade, but this method appears to have been removed in cargo-edit v0.10 and we couldn't find any information in the CHANGELOG regarding what happened to it or what to replace it with.

What should we use in newer versions of cargo-edit to perform a similar function? We also currently offer a --dry-run option and ideally we'd like to preserve that functionality as well if possible.

See also: rustsec/rustsec#801

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions