noir-sync-update

You can automate lockfile updates by running a coordinated process that refreshes Cargo.lock and yarn.lock, formats the codebase, and commits changes across noir, avm-transpiler, and yarn-project repositories.

Submodule sync involves verifying git status from the repository root, running bootstrap.sh, updating Cargo.lock and yarn.lock explicitly, formatting code, and committing coordinated changes across affected repos.

Yes, a clean git status from the repository root is strictly enforced before updating Cargo.lock and yarn.lock to ensure no uncommitted changes interfere with the coordinated submodule sync.

Updating the noir submodule requires coordinating changes across avm-transpiler and yarn-project because the update triggers downstream dependencies that must be synchronized in Cargo.lock and yarn.lock to maintain project hygiene.

No, bootstrap.sh is an explicit step in the noir submodule sync process, required to set up the environment before updating Cargo.lock and yarn.lock and formatting the codebase for the final commit.