fix: accept published installer migration checksums

This commit is contained in:
Colin
2026-06-04 12:23:29 -04:00
parent e8dc420b4d
commit b8e15c7a98
12 changed files with 198 additions and 3 deletions

View File

@@ -125,6 +125,11 @@ The checksum is calculated from the migration definition. If an applied
migration's checksum changes, the installer must warn and refuse to silently
re-run it. Fix-forward migrations should use a new migration id.
Migration records may pin a stable `checksum` and list `legacyChecksums` for
checksums already written by published packages. This is only for compatibility
with released install state; new behavior should still ship as a new migration
id rather than mutating an already-applied migration in place.
## Migration Record
Each migration exports a plain record plus pure planning logic.