Supabase APIBreaking changecritical
Supabase CLI v3 defaults to local, requires --remote on Nov 2, 2026
- Detected
- Nov 4, 2026
- Effective
- Nov 2, 2026(took effect 14 days ago)
- Confidence
- 98%
What changed
Supabase CLI v3.0.0 changes default command targets (local instead of hosted), requires explicit --remote and --yes flags for hosted/unattended operations, removes deprecated commands and config keys, and is now installed by default via npm, Homebrew, Scoop, and setup-cli. Pipelines and CI scripts that install the latest CLI without pinning a version are immediately affected.
What to do
Add --remote to any command targeting a hosted project, add --yes to unattended hosted changes in CI, rename [inbucket] to [local_smtp] in config.toml, and pin v2 (npm install supabase@v2.stable) if not ready to migrate.
Affected
param: --remoteparam: --yesparam: --linkedparam: --project-refparam: --db-urlendpoint: db pushendpoint: db pullendpoint: db dumpendpoint: db diffendpoint: migration listendpoint: gen typesendpoint: functions deployendpoint: secrets setendpoint: secrets unsetendpoint: config pushmodel: [inbucket] config sectionmodel: [local_smtp] config sectionmodel: supabase-go executableSource: 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