Docs: SpacetimeDB 2.0 migration guide#4383
Merged
Conversation
This section is about user schema migrations, not SpacetimeDB version upgrades.
…lockworklabs/SpacetimeDB into phoebe/docs/v2-migration-guide
We've baked `/docs/upgrade` into a few places, including the CLI's help text. I would prefer to use the slug previously listed in this file, but I don't want to push changes to the CLI at this point.
cloutiertyler
approved these changes
Feb 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Changes
Expanded and reorganized the 2.0 migration guide, and also deleted a file that was in the wrong place. (The word "migration" is overloaded...)
API and ABI breaking changes
N/a
Expected complexity level and risk
Like, 1 I guess, since this isn't code? But we should be careful to get this right.
Testing
basic-rstemplate and got 'em to build.play_damage_animation, bindingtargetandamount), and changing one table name that was used in two examples, but otherwise everything is valid.