Skip to main content

LOCK

Constant LOCK 

Source
pub const LOCK: &str = "apps/majordomus-cli/Cargo.lock";
Expand description

The lock file, which records the crate’s own version alongside every dependency’s.

Not a declaration — cargo derives it from the manifest, and nobody chooses the value. It is a tracked record, though, and the build runs --locked: a bump that raised the manifest and left the lock behind made the next build fail with cannot update the lock file ... because --locked was passed, which reads as a toolchain fault rather than as a half-applied bump, and it fails every launcher call — the git hooks, the MCP server — until something rebuilds without --locked. So the writer keeps the crate’s own entry in step, by cargo’s rule, in the same command that raises the manifest.