cargo-lock-manager

The --locked flag fails in CI/CD when Cargo.lock drifts from your workspace dependencies. This Skill identifies the drift, updates the lockfile, and commits changes to ensure pipelines pass.

Update Cargo.lock across a workspace by running cargo update to align dependencies. This Skill automates the update process, re-runs checks to verify reproducibility, and commits the lockfile changes.

Yes, git is required alongside cargo to resolve lockfile issues. This Skill uses git to commit Cargo.lock updates directly to your repository, ensuring CI/CD pipelines and PR workflows stay synchronized.

The best way to prevent CI failures from missing lock commits is to check Cargo.lock status for workspace drift and commit updates before pipeline execution. This Skill aligns dependencies and applies fixes directly in PRs.

Yes, you can resolve dependency drift in local development. It checks workspace member status, applies cargo update fixes, and runs locked checks to ensure your local environment matches the CI/CD configuration.