What problem does it solve?
Manage world migrations and handle breaking changes when updating deployed Dojo worlds so teams can upgrade versions, add models or systems, and preserve data integrity without unexpected downtime or data loss.
Core Features & Use Cases
- Inspection and analysis: Run pre-migration inspection to list new and modified models, systems, and resource status to identify additive versus breaking changes.
- Migration planning: Support additive migrations, parallel model/versioning strategies, or full data migration systems to transform existing data when schemas change.
- Execution and verification: Integrate build, test, and migrate steps (inspect, build, test, migrate) and provide a checklist and troubleshooting guidance for profiles, funds, and compatibility.
- Version upgrades: Guide updating Scarb/dojo dependencies, reviewing changelogs, and regenerating client bindings and indexers after migrations.
- Use case: Upgrade a live Dojo world to dojo 1.8.0 while preserving player data by either deploying a new world seed, running a migrator system to transform models, or keeping parallel model versions during rollout.
Quick Start
Migrate my changes to the deployed world using sozo inspect, then sozo build, sozo test, and sozo migrate with the appropriate profile.
