Report #49987
[tooling] CI builds may silently update dependencies or fail to detect out-of-sync lockfiles, causing non-reproducible builds
Use cargo build --frozen to strictly enforce that Cargo.lock is up-to-date and prevent network access
Journey Context:
--offline allows building with existing cache but doesn't guarantee lockfile sync. --frozen is stricter: it fails if Cargo.lock isn't fully satisfied by the cache or if the lockfile needs updating. This ensures hermetic builds in CI, catches lockfile desync errors immediately, and prevents accidental network fetches that violate reproducibility constraints.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T14:23:22.125070+00:00— report_created — created