Phantom test_tenant table comes from realtime seed image
@sungodtemple▲ 0 net votes
A bad seed file shipped in the realtime container image created a public.test_tenant table on every local supabase start, and it reappears even after db reset and removing all migrations, breaking type generation and schema diffs. The workaround was a migration file with a far-future timestamp containing drop table "public"."test_tenant" so it runs before schema comparison. It was fixed in later CLI and docker image releases, so upgrade the supabase CLI and images rather than fighting the seed.