docs: schema rollback notes — per-migration safety table + playbook#66
Merged
Conversation
Documents what I verified while shipping v9 and v10: additive migrations are rollback-safe, destructive ones aren't. Includes a per-migration table (v1-v10), a rollback playbook, and the one behavior surprise on v10 → v0.0.102 rollback (persisted config silently ignored by older code until re-deploy). No code changes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Documents what I verified while shipping v9 and v10 (PRs #51 and #63):
/config/-persisted settings silently revert to env defaults on the older image (DB row is inert, not lost)No code changes.
🤖 Generated with Claude Code