cargo-lock-manager
Original:🇺🇸 English
Translated
2 scripts
Manages Cargo.lock file updates and resolves --locked flag issues in CI/CD. Triggers when user mentions: - "cargo test --locked failed" - "cannot update the lock file" - "Cargo.lock is out of date" - "PR failed with --locked error" - "fix Cargo.lock"
2installs
Sourcedifferent-ai/openwork
Added on
NPX Install
npx skill4agent add different-ai/openwork cargo-lock-managerTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Quick Usage (Already Configured)
Check Cargo.lock status
bash
cd packages/desktop/src-tauri
cargo check --locked 2>&1 | head -20Update Cargo.lock locally
bash
cd packages/desktop/src-tauri
cargo update --workspaceTest with --locked after update
bash
cd packages/desktop/src-tauri
cargo test --lockedCommon Gotchas
- The flag prevents automatic updates to Cargo.lock, which is good for reproducible builds but fails when dependencies change.
--locked - PRs often fail because the lock file wasn't committed after dependency updates.
- Running without
cargo updatemay not update all workspace members.--workspace
When CI Fails with --locked
Option 1: Update lock file and commit (Recommended)
bash
cd packages/desktop/src-tauri
cargo update --workspace
git add Cargo.lock
git commit -m "chore: update Cargo.lock"
git pushOption 2: Use --offline flag (for air-gapped environments)
bash
cargo test --manifest-path packages/desktop/src-tauri/Cargo.toml --offlineFirst-Time Setup (If Not Configured)
No setup required. This skill assumes:
- Rust/Cargo is installed
- You're in the openwork repository
- The Tauri app is in
packages/desktop/src-tauri/
Prevention Tips
- Always run or
cargo checkafter modifyingcargo buildfilesCargo.toml - Include changes in the same commit as dependency updates
Cargo.lock - Consider adding a pre-commit hook to verify lock file is up to date