Cargo.lock drift blocks every rebuild #23

New issue

Closed

opened 2026-05-12 14:57:06 +00:00 by zaelgohary · 1 comment

zaelgohary commented

2026-05-12 14:57:06 +00:00

Member

cargo metadata --locked fails on current development:

error: cannot update the lock file ... because --locked was passed to prevent this
help: to generate the lock file without accessing the network, remove the --locked flag and use --offline instead.

herodev's hero-rebuild-all runs a pre-build cargo metadata --locked guard and reports FAIL drift hero_agent for every sync since the drift landed (currently 3h+ stale binary at /home/zainab/hero/bin/hero_agent).

Fix: cargo update in the repo, commit the regenerated Cargo.lock, push to development.

`cargo metadata --locked` fails on current `development`: ``` error: cannot update the lock file ... because --locked was passed to prevent this help: to generate the lock file without accessing the network, remove the --locked flag and use --offline instead. ``` herodev's `hero-rebuild-all` runs a pre-build `cargo metadata --locked` guard and reports `FAIL drift hero_agent` for every sync since the drift landed (currently 3h+ stale binary at `/home/zainab/hero/bin/hero_agent`). Fix: `cargo update` in the repo, commit the regenerated `Cargo.lock`, push to development.