Evan JarrettandClaude Opus 5 c1604b9a04 test/e2e: key DB snapshots on the migration set, not the highest version ...

Batching reorders migrations. val/04-oauth carries e75b2e2 (commit 48 of the
range), whose migration is 0031, while 0028-0030 only arrive in batches 09, 12
and 14. So val/04 holds {..0027, 0031} and val/09 holds {..0027, 0028, 0031}.
Both have a max version of 0031, so keying the snapshot on the max would
restore val/04's database onto val/09 — a database missing 0028's schema while
schema_migrations claims otherwise.

Snapshots are now keyed on a fingerprint of every migration file present, which
distinguishes those two states. The max version is kept in the filename purely
so the directory stays readable.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-25 16:34:25 -05:00

..

e2e

test/e2e: key DB snapshots on the migration set, not the highest version

2026-08-25 16:34:25 -05:00

integration

auth: make anonymous pull work, and let the hold decide it

2026-08-10 21:43:32 -05:00

stripe-integration

billing: make Stripe webhook delivery idempotent and retryable

2026-08-09 21:14:58 -05:00