cargo-lock-manager

Cargo.lock --locked checks fail in CI when the lock file is out of sync with Cargo.toml dependencies. This Skill detects lockfile mismatches across Rust workspace crates and provides remediation steps to refresh and commit the updated lock file.

To fix an out-of-date Cargo.lock in a Rust workspace, run the provided scripts to validate consistency using cargo check and refresh dependencies with cargo update. This ensures the lock file reflects all workspace crates before committing the resolved changes.

Yes, you need the cargo dependency installed to manage lockfile synchronization. The Skill leverages cargo commands to validate manifests and update the lock file, requiring access to Cargo.toml files within your Rust workspace environment.

The best way to prevent CI failures from Cargo.lock drift is to automate detection and updates during pre-merge checks. This Skill guides CI/CD workflows to identify out-of-date locks and apply cargo update to maintain reproducible builds across multi-crate workspaces.

Yes, you can use this to update Cargo.lock across multiple crates. It is specifically designed for Rust workspace projects, ensuring the lock file accurately reflects all dependencies across workspace members during local development and CI pipelines.