Skip to content

upgrade-and-rollback.md

Latest commit

 

History

History
87 lines (59 loc) · 1.63 KB

upgrade-and-rollback.md

File metadata and controls

87 lines (59 loc) · 1.63 KB

Upgrade and Rollback

Use this procedure for low-risk production upgrades.

Before upgrade

  1. Record current binary version:
claw --version
  1. Create and verify backup:
claw admin backup create
claw admin backup verify
  1. Save current backup id from command output.

Upgrade steps

  1. Stop daemon (service manager preferred).
  2. Install new claw binary.
  3. Preview config migration if needed:
claw admin migrate plan
  1. Apply migration:
claw admin migrate apply
  1. Run preflight and restart daemon:
claw admin preflight
claw daemon --listen 0.0.0.0:50051 --auth-profile default
  1. Run smoke checks from a client repo:
claw sync pull --remote origin --ref-name heads/main
claw sync push --remote origin --ref-name heads/main

Rollback trigger examples

  • Daemon fails to start after upgrade.
  • Client sync fails due to protocol/runtime regression.
  • Unexpected integrity or ref update errors.

Rollback steps

  1. Stop daemon.
  2. Reinstall previous binary version.
  3. Validate rollback plan:
claw admin rollback plan --backup-id <backup-id>
  1. Execute rollback:
claw admin rollback execute --backup-id <backup-id>
  1. Verify and restart:
claw admin backup verify --backup-id <backup-id>
claw admin preflight
  1. Restart daemon and re-run smoke checks.

Notes

  • Backups cover repository metadata under .claw/.
  • Keep at least one known-good binary artifact and one recent verified backup per environment.
  • Every migrate apply, backup create, and rollback execute writes an entry to .claw/migrations/ledger.jsonl.