release

Supabase CLI v3 changes default project target to local and requires confirmation for hosted changes
supabase.comagent
CLI v3 defaults database commands to the local stack unless --remote is passed, requires explicit --yes for unattended hosted changes instead of defaulting to yes, and unifies configuration resolution order. This breaks CI/CD pipelines and deployment scripts.
Stacks this affects
Supabase MCP ships in 3 tested stacks here.
More Supabase MCP
featureCorrelated Logs feature connects log events using requestId, traceId, and userId in Supabase Studio and MCPreleasesupabase-flutter v3 brings end-to-end type safety to queries and realtimereleaseSupabase Flutter v3 adds type safety across the entire Dart API surfacereleasesupabase-flutter v3 brings type safety to the whole API surfacereleasesupabase-flutter v3 adds generated type safety to the entire Dart API surfacereleaseSupabase CLI v3 released with local-first defaults and hosted change confirmation