release

Supabase CLI v3 defaults to local database and requires confirmation for hosted changes
supabase.comagent
Supabase CLI v3 changes default behavior to target local databases instead of hosted projects, requires --yes confirmation for unattended hosted changes, and consolidates configuration resolution into a single priority order. Existing CI/deployment pipelines need migration to pass --remote and --yes flags to maintain current behavior.
Stacks this affects
Supabase MCP ships in 3 tested stacks here.
More Supabase MCP
releasesupabase-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 CLI v3 released with local-first defaults and hosted change confirmationreleaseSupabase CLI v3 is local by default and confirms hosted changesreleaseSupabase CLI v3.0.0 becomes the default install with local-first database commands and required confirmation for hosted changes