Unified · Split
| @@ -0,0 +1,15 @@ | ||
| 1 | +--- | |
| 2 | +"executor": patch | |
| 3 | +--- | |
| 4 | + | |
| 5 | +**Hardened the local v1→v2 database upgrade** | |
| 6 | + | |
| 7 | +Upgrading a local database created by an older (v1) release is now resilient to | |
| 8 | +interrupted or partially-written upgrade state: | |
| 9 | + | |
| 10 | +- The one-time upgrade is recorded in the migration ledger, so it is never | |
| 11 | + re-attempted on later boots. Databases that have already upgraded are detected | |
| 12 | + from the ledger and skip the upgrade path entirely. | |
| 13 | +- Replaying the legacy schema now tolerates a missing or truncated migration | |
| 14 | + journal instead of failing to start, so a database left in a half-written | |
| 15 | + state from a previous crash boots cleanly. | |