Repository navigation
docs: treat shipped SQLite migration SQL as immutable - #33
Merged
Merged
Conversation
v0.2.19 retabbed an applied migration and existing databases panic on boot. Record the rule in AGENTS.md and DESIGN.md so whitespace-only rewrites of shipped SQL do not ship again.
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
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.
Summary
AGENTS.md: never rewrite a shipped SQLite migration; schema changes go in a new numbered file.docs/DESIGN.md.Whitespace, comments, and indent inside the raw SQL string all change SHA-256. Existing databases panic on boot with
checksum mismatch, and the host updater rolls back.Test plan
AGENTS.mdDo/Don't,docs/DESIGN.mdSQLite migrations + Console IA order,CONTRIBUTING.md, anddocs/DEVELOPMENT.mdrelease checklist