cargo-edit icon indicating copy to clipboard operation
cargo-edit copied to clipboard

A utility for managing cargo dependencies from the command line.

Results 90 cargo-edit issues
Sort by recently updated
recently updated
newest added

`cargo add` and `cargo rm` both use dependency names. `cargo upgrade` used to also use dependencies names but in the current pass I switched to crate names to be more...

question
cargo-upgrade

It looks like you are currently depending on git2 v0.14. v0.15 fixes a [segfault while iterating over config entries](https://github.com/rust-lang/git2-rs/issues/836), so it might be a good idea to upgrade.

bug

For library crates, updating all dependency requirements in `Cargo.toml` to the latest semver-compatible versions is harmful to the ecosystem, as this makes it harder to resolve versions in case of...

enhancement
cargo-upgrade

If we treat `cargo upgrade` as a replacement for `cargo update`, #790 provided us limited support for `cargo update --precise` but doesn't help when you want to set it for...

bug
cargo-upgrade

With #790 being fixed with #795, there are "last writer win" issues where one `cargo update --aggressive` might do the precise version selection from a previous `cargo update`. I assume...

bug
cargo-upgrade

as per https://github.com/rust-lang/compiler-team/pull/89#issuecomment-494693064 what do you think about having https://github.com/rust-lang/rust/issues/57443 in `cargo edit`. Maybe as `cargo edit sync-with-lockfile`? related: https://github.com/killercup/cargo-edit/issues/41 cc @polybuildr

enhancement
cargo-upgrade

When I run `cargo-upgrade upgrade` I get: ``` Error: The repo at path /home/gabor/.cargo/registry/index/github.com-1ecc6299db9ec823 is unusable due to having an invalid HEAD reference: reference 'refs/heads/main' not found; class=Reference (4); code=NotFound...

This will forever be a draft, unless someone adopts it of course. But I hope it will help moving things forward. This implements preliminary support for sparse indices. * All...

It is slow. Is there a way to edit `Cargo.toml` only without any checks? I need to set exact versions of several dependencies in a set of projects and bump...

For example, I have a dependencies with version `2.0.0-beta`. When I use cargo upgrade, it always changes the version to `2.0.0-beta.9`

cargo-upgrade