noir-sync-update

To update lockfiles after a Noir git submodule update, you must refresh dependencies in both the Rust and JavaScript workspaces. This workflow targets the avm-transpiler Cargo.lock with scoped cargo update flags and runs yarn install to synchronize yarn.lock in the yarn-project directory.

Updating the Noir git submodule breaks CI builds when downstream lockfiles and project formatting fall out of sync with the new compiler commit. This workflow resolves the breakages by refreshing Cargo.lock, yarn.lock, and running the noir-projects formatter to match CI expectations.

The best way to sync Noir project formatting is to run the ./bootstrap.sh format script in the noir-projects directory. This applies formatting changes introduced by the updated compiler so the repository matches what CI expects before committing.

To run a targeted cargo update for only Noir-repo dependencies, use scoped cargo update package flags limited to Noir-repo packages within the avm-transpiler directory. This prevents unwanted version bumps across unrelated crates while aligning the Rust toolchain.

Yes, you need to verify git status from the repository root after updating lockfiles and formatting projects. This workflow enforces verification via git status to ensure all modifications to Cargo.lock, yarn.lock, and noir-projects are properly tracked before committing.

Yes, you can use this workflow for multi-repo blockchain development environments because it specifically targets the Rust AVM transpiler lockfile, the Yarn workspace lockfile, and Noir projects formatter across distinct repositories to maintain deterministic dependency alignment.