supabase db schema declarative sync adds --no-apply
Introduced 2026-05-21 · score 0.96
HOW TO USE IT
When you need a generated declarative-schema migration without applying it locally, run `supabase db schema declarative sync -f <migration_name> --no-apply` to write the migration and stop without prompting. The command requires declarative schema support to be enabled.
supabase db schema declarative sync -f <migration_name> --no-applyWHY THIS HELPS
Generate a declarative schema migration in CI or a review workflow and inspect the diff before changing the local database.
REQUIREMENTS AND LIMITATIONS
- Version: v2.101.0
- --no-apply: Generate the migration file without prompting or applying it locally.
- -f, --file <string>: Save the schema diff to a new migration file; the example uses this to name it.
- --experimental: Enable experimental features for a single run; alternatively enable `[experimental.pgdelta]` in config.toml.
- Prerequisite: Requires `--experimental` or `[experimental.pgdelta] enabled = true` in config.toml.
- Prerequisite: The declarative sync command requires the pg-delta engine; it does not run on the legacy migra engine.
- `--no-apply` overrides the global `--yes`.
- `--no-apply` cannot be combined with `--apply`.
FIRST-PARTY EVIDENCE
- https://github.com/supabase/cli/releases/tag/v2.101.0
- https://supabase.com/docs/guides/local-development/declarative-database-schemas
- https://supabase.com/docs/reference/cli/global-flags
Check the installed version and the source before using it. Entry JSON