Strata · Errors

EDITED

planMigrations reports EDITED when the steps of an applied migration no longer match the checksum recorded in the ledger. Here a default was added to the bookings table inside theatre.app/2 after it was applied. refuseProblems, which migrate calls on every plan, throws the error.

Ledger row: migration 2

{
  sequence: 'theatre.app',
  n: 2,
  checksum: 'db5c8c8dc31eefb2a450f0915d96a5d592e73e067c8d7c7bffd5c3e5c74f2d99',
  description: 'Bookings',
  appliedAt: '2026-09-01T03:00:00Z',
}

Code: migration 2

{
  checksum: 'fca801ee433cffb3201224ba6a6e8a7573fe7b2a5daee9ba12186b9368df9f14',
  steps: [
    {
      kind: 'sql',
      sql: 'CREATE TABLE bookings (id text PRIMARY KEY, night date REFERENCES shows, seats int NOT NULL DEFAULT 1)',
    },
  ],
}

Error

EDITED
The migrations cannot be applied safely.
  EDITED: theatre.app/2 ("Bookings") was applied 2026-09-01T03:00:00Z and its steps have changed
  since. An applied migration is history — append a new one.

Output matches the expected value

Runs in this page on the installed package. The input and the expected output are defined by the example.