update-crates

To update Rust crate dependencies without breaking the lockfile, you can refresh Cargo.lock with semver-compatible changes while keeping manifests unchanged. This preserves existing pins and requires formatting, clippy, and tests to pass.

You can upgrade Cargo.toml major versions while preserving the pinned Rust toolchain. The update process respects version caps, comments, and toolchain constraints, ensuring deliberate major bumps do not override existing environment pins.

The best way to perform semver-compatible dependency updates across a Rust workspace is to refresh the lockfile while respecting existing manifest pins and version caps. This ensures workspace tests and clippy checks verify compatibility.

Updating workspace dependencies does run formatting and clippy checks before merging. Standard verification steps are required to ensure dependency changes do not introduce formatting violations or lint errors into the Rust workspace.

A Cargo lockfile update might break a pinned Rust 1.95.0 toolchain constraint if version caps are ignored. Safe dependency maintenance preserves this exact toolchain version while applying semver-compatible updates.

You need to update Cargo.toml version requirements instead of just refreshing the lockfile when a deliberate major-version upgrade is required. Lockfile refreshes only handle semver-compatible dependency changes without altering manifest pins.