Wanjohi bd163392ca fix(core): declare the claim column the migration adds ...

The migration adds session.claim_token, but neither the schema nor the
snapshot knew about it. Nothing breaks today because the two agree with
each other; it breaks the moment someone declares the field, because
generate then diffs against a snapshot without it and emits

    ALTER TABLE "session" ADD COLUMN "claim_token" text;

which fails on every database the migration has already run against.

Declared with no writer yet, so the schema, the snapshot and the
database say the same thing.

2026-09-05 00:10:57 +03:00

..

_journal.json

feat(core): make one address one account, on rows that never had one

2026-09-05 00:02:00 +03:00

0000_snapshot.json

feat: Sync to OSS repo

2026-08-06 22:13:51 +03:00

0001_snapshot.json

feat: Sync to OSS repo

2026-08-06 22:13:51 +03:00

0002_snapshot.json

feat: Sync to OSS repo

2026-08-06 22:13:51 +03:00

0003_snapshot.json

feat: Sync to OSS repo

2026-08-06 22:13:51 +03:00

0004_snapshot.json

feat: Sync to OSS repo

2026-08-06 22:13:51 +03:00

0005_snapshot.json

feat: Sync to OSS repo

2026-08-06 22:13:51 +03:00

0006_snapshot.json

feat: bring the control plane up to date

2026-08-26 17:48:46 +03:00

0007_snapshot.json

feat(core): a box is a row, a session is the billing unit

2026-09-03 21:39:27 +03:00

0008_snapshot.json

fix(api): a box gets one run, and a stopped run keeps no address

2026-09-04 21:58:57 +03:00

0009_snapshot.json

fix(core): declare the claim column the migration adds

2026-09-05 00:10:57 +03:00