fleet-updating-lockstep

Automating lockstep.json drift resolution across submodules involves fetching upstream tags, selecting stable targets, and performing atomic commits for each version-pin row. This skill pipelines each row through a workflow to resolve, bump, validate, and commit changes independently.

Atomic version bumping for pnpm fleets updates lockstep manifests consistently across multi-repo environments. It applies per-row workflows using pnpm and git tooling to ensure consistent submodule annotations and safe, synchronized updates.

You cannot fully automate non-version-pin drift like file-fork, feature-parity, spec-conformance, or lang-parity with this workflow. It surfaces advisory results for these categories to guide human review and requires manual approval for non-automated actions.

The lockstep bumping workflow requires pnpm and git tooling to operate across multi-repo fleets. You need a repository containing a lockstep.json manifest and the ability to run pnpm run lockstep --json to fetch the initial drift data.

The best way to sync lockstep.json in a standalone repository is running the fleet-updating-lockstep skill directly on the repo. It executes the per-row workflow to resolve, bump, validate, and commit version-pin changes independently without needing the umbrella workflow.