Add a database migration

SupaCloud uses sequential, numbered SQL migrations in server/migrations/.

Steps

1. Find the next number — safely. Migration numbers are a shared namespace across parallel developers and worktrees. Before picking a number:

   git fetch
   ls server/migrations/        # scan the highest number on main

   Also scan any sibling worktrees. Then take the next free number.

2. Add the file as NNN_short_description.sql in server/migrations/.

3. Verify it applies and the server still type-checks:

   cd server && cargo check

Caution

Never edit an applied migration. Migrations are applied once and tracked by filename; changing one that has already run will not re-run and will diverge environments. Add a new migration instead.

Note

Gaps in the sequence are fine — sqlx tracks migrations by filename, not by a contiguous range. A few historical numbers are unused.

See also

• Local development setup