Skip to main content
Version: MVP

Updating Craik

2 min readFor operatorsUpdated 2026-05-22

What you'll do

Read the non-mutating update guidance craik update prints, then run the recommended manual flow. craik update never modifies the installed package, source checkouts, remote release metadata, or local state.

Non-mutating by default.

Update guidance is informational. Craik will not silently upgrade itself or migrate local state.

Run it​

craik update

For automation, use check mode:

craik update --check

Output covers:

Installed version

Supported Python range

Local store migration compatibility

Contract compatibility

Manual update steps

Mode

check for automation, manual for operator guidance.

Boundaries

For what Craik will not do automatically.

  1. Review release notes and migration notes.
  2. Run craik doctor.
  3. Update Craik with the package manager or source checkout that installed it.
  4. Run craik doctor again.
  5. Run project validation before starting the gateway.

Patch first, then minor.

For published 0.x.y patch releases, prefer the newest patch in the current minor line unless release notes call for a migration. Capability-bearing 0.x.0 upgrades are minor compatibility events until Craik reaches 1.0.0.

Future migration commands may add explicit local-state migrations, but update guidance remains non-mutating by default.

What's next​

GuideDoctor diagnosticsThe health check to run before and after an upgrade.GuideLocal store migrationsHow forward-only migrations run during LocalStore.initialize().GuideRelease managementHow the releases you're consuming are produced.