Supabase
Releases
Security & compliance
Stability
Migration drops a table or column with no rollback path
Part of the Migration & schema safety check · fix arrives as a pull request
What it is
A migration executes a DROP that permanently removes a table or column, with no IF EXISTS guard and no companion rollback.
Why it matters
The data is gone at the moment it runs, and a failed deploy has no automated way back. Recovery becomes a restore from backup, which loses everything written since.
How to fix it
Archive first — CREATE TABLE thing_backup AS SELECT * FROM thing; — add IF EXISTS to the drop, and write the down-migration that recreates the object. Better still, stop writing to it in one release and drop it in a later one.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.