Supabase's October 30 change: don't fix "permission denied" by reopening your tables

Starting October 30, 2026, Supabase will apply a new default to all existing projects. New tables created in the public schema will no longer automatically receive select, insert, update, and delete privileges for anon, authenticated, and service_role roles. Consequently, these tables remain unreachable through supabase-js, REST, and GraphQL until access is explicitly granted. Users may encounter Postgres error 42501, indicating permission denied, even if RLS policies are correctly configured for the specific table.