cargo-edit CLI
Additional Cargo commands update dependency requirements and package versions, with dry-run previews for agent review.
- 3,472 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Commands modify manifests and may update resolved dependencies; unsuitable upgrades can break builds or behavior.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/cargo-editDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Commands modify manifests and may update resolved dependencies; unsuitable upgrades can break builds or behavior.
This is third-party code. Review the repository files before installing.
What it does
cargo-edit adds Rust manifest-editing commands. Agents can update dependency requirements with `cargo upgrade` or change package versions with `cargo set-version`. Dry runs let users inspect proposed changes before writing. The current package focuses on those commands; dependency add and removal are already part of Cargo. Users select packages, exclusions and compatibility policy, then review manifests and test the updated project.
Who it is for. Rust library maintainers regularly updating dependency constraints and preparing package versions.
Good fit when
- Cargo.toml requirements need updating beyond Cargo.lock resolution.
- An agent prepares a package-version bump with a preview diff.
- Several pinned dependencies must stay outside a broad upgrade.
- Selected workspace packages need coordinated version changes.
Not a fit when
- You only need ordinary dependency addition in modern Cargo.
- You expect new dependencies to be automatically compatible with project code.
- Manifest changes cannot be reviewed and tested.
Example request
Show a cargo upgrade dry run for the selected dependency and explain the Cargo.toml change without writing it.Limitations
Installation needs a recent Rust and Cargo; Ubuntu also requires libssl-dev and pkg-config per the source. Upgrade changes manifest requirements, which differs from updating only lockfile resolution. Incompatible and pinned versions have separate controls; inspect them before broad changes. A changed manifest does not prove successful builds or behavior, so run project checks after reviewing the patch.
How to disable. Stop the extra commands and uninstall cargo-edit if needed. Revert applied manifest and lockfile changes separately through Git or backups.
FAQ
How do upgrade and update differ?
`cargo upgrade` changes requirements in `Cargo.toml`; `cargo update` refreshes resolved versions in `Cargo.lock`.
Can I preview changes?
Yes. Both commands support `--dry-run`.
Is the package needed for `cargo add`?
No. Cargo has included that command since version 1.62.
How do I exclude a package?
Use `--exclude` with its name.
Can workspace versions be changed?
Yes. `cargo set-version` supports `--workspace` and package selection.
Discussion
No questions or reviews yet.
Related
CLI toolsRenovate CLI brings dependency updates across ecosystems into pull requests governed by the team’s rules and schedule.
Three skills and a clippy config: an agent writes, reviews and ports idiomatic Rust, and CI enforces the checkable rules
Rust documentation MCP server: an agent searches crate items, reads source code and inspects the dependency tree.
uutils coreutils provides Rust file utilities that can sit beside system commands for comparisons with existing scripts.
The CLI builds Rust into WebAssembly and prepares a JavaScript package for agent-assisted integration of a reviewed module.
The version manager selects runtimes from project settings so agents run tools in an agreed development environment.
README in short
Upgrade controls distinguish compatible, incompatible and pinned requirements. Version changes support major, minor and patch increments.