Restore startup compatibility with native migration history

conrad commented

2026-09-06 16:42:33 -04:00

Owner

Production exits at startup because its SQLite migration history includes m20260906_000046_eink_sync_receipts, absent from main. Recover the original e-reader receipts, native authorization and device authorization migration definitions from the native checkout, preserving their exact names and SQL. Register them alongside the archive migration; do not edit production data or migration history. This adds schema compatibility only, without adding native authentication endpoints.

Validation: all 74 migration tests pass. A regression fixture creates the native deployment schema, inserts an authorization request, then applies and reapplies the main migrator while checking that the row survives and foreign keys remain valid. Formatting and diff checks pass.

The preceding reader release passed full CI, but could not boot against this already-upgraded database. This repair will be deployed directly using the same production Dockerfile and Fly configuration for incident recovery; the redundant automatic deployment will be cancelled.

Production exits at startup because its SQLite migration history includes m20260906_000046_eink_sync_receipts, absent from main. Recover the original e-reader receipts, native authorization and device authorization migration definitions from the native checkout, preserving their exact names and SQL. Register them alongside the archive migration; do not edit production data or migration history. This adds schema compatibility only, without adding native authentication endpoints. Validation: all 74 migration tests pass. A regression fixture creates the native deployment schema, inserts an authorization request, then applies and reapplies the main migrator while checking that the row survives and foreign keys remain valid. Formatting and diff checks pass. The preceding reader release passed full CI, but could not boot against this already-upgraded database. This repair will be deployed directly using the same production Dockerfile and Fly configuration for incident recovery; the redundant automatic deployment will be cancelled.

conrad added 1 commit

2026-09-06 16:42:35 -04:00

Recognize native migrations already applied to production

deploy-fly / validate (push) Has been cancelled

Details

deploy-fly / deploy (push) Has been cancelled

Details

161ed119b6

conrad merged commit 161ed119b6 into main

2026-09-06 16:43:36 -04:00

Rows
Columns

Restore startup compatibility with native migration history #18