Updating the Blueprints submodule

Commands and checks to move blueprints/ to a newer upstream commit — no methodology prose.

Guide · Updated · Source

What it is

Commands and checks to move blueprints/ to a newer upstream commit — no methodology prose.

When to use it

Use this guide on a schedule, after upstream fixes, or when you need a feature that landed in autowww/blueprints.

Prerequisites

  • blueprints/ is a git submodule at the repository root (not a stray copy without git metadata).
  • You have permission to commit submodule pointer updates on your default branch.

Choose a topic

Topic Page
Routine bump — fetch, pull, commit pointer Routine bump
Validate and test — CI, check, frozen tree Validate and test
Recovery — lifecycle, rollback, conflicts Recovery and rollback

Quick flow: routine → validate → if anything fails, recovery and Troubleshooting.

Update lifecycle (visual)

Submodule update lifecycle

Pick a guide topic, run the governed bump workflow, and reach a reviewable outcome—or recovery if validation fails.

  1. Choose a topicSelect routine bump, validate, or recovery from the topic table.
  2. StartBegin from prerequisites with a submodule at the repository root.
  3. Core steps (see walkthrough below)Execute fetch, pull, validate, and test per your chosen topic page.
  4. OutcomeA committed submodule pointer or a documented rollback path.

What to do next