Supabase APIBreaking changehigh
supabase-flutter v3 breaks Dart/Flutter API surface with stable release on Nov 11, 2026
- Detected
- Nov 7, 2026
- Effective
- Nov 11, 2026(took effect 5 days ago)
- Confidence
- 97%
What changed
supabase-flutter v3 introduces sweeping breaking changes to the Flutter/Dart client library, including renamed packages, changed API signatures, new type system, and altered defaults (e.g. order() sort direction). Stable release is planned for November 11, 2026, with v2 receiving security fixes for 6 months afterward.
What to do
Before upgrading: add ascending: false to all order() calls relying on descending order while still on v2. Then bump to ^3.0.0, replace renamed packages (gotrue→supabase_auth, realtime_client→supabase_realtime, etc.), fix compile errors per the migration guide, and coordinate simultaneous release of apps sharing realtime broadcast channels.
Affected
model: supabase_fluttermodel: supabasemodel: gotrue (renamed to supabase_auth)model: realtime_client (renamed to supabase_realtime)model: storage_client (renamed to supabase_storage)model: functions_client (renamed to supabase_functions)endpoint: supabase.rpcendpoint: supabase.tableparam: order() ascending defaultparam: Supabase.initialize anonKey → publishableKeySource: supabase.com (Supabase's own page, checked by Breakwatch)
Is your code affected?
Search your repositories for the Supabase SDK and the names above:
Or let Breakwatch do it: connect a repo and see which files call Supabase, then get the next change as an alert pointing at those files. Check a repo free