- Create a branch in the game repository.
- Install the exact SDK and CLI versions described by the target release’s documentation.
- Run type checks, invariants, saved scenarios, seeded playthroughs, and replay tests.
- Review scene and component behavior in the local table.
- Commit the dependency lockfile and deploy a new game release.
Never overwrite old R2 objects to perform an upgrade. Older rooms reference their original manifest and need those files for reconnect and replay.
Maintenance fixes
For a fix to an older SDK line, branch from that line’s release tag. Publish a new patch with its own docs snapshot and line tag. Keep latest on the newer line. The release automation applies this rule separately from the readable version in a game’s manifest.
Compatibility failures
A tooling host API mismatch should name the installed SDK and required API. A network protocol mismatch must fail without transforming saved state. Fix the adapter or use the supported CLI/platform generation rather than relabeling a snapshot.