github supabase/cli v3.2.0

one hour ago

Supabase CLI v3.2.0 — 2026-11-16

This release adds config tooling (config validate and config convert), HTTPS on the local API for the experimental stack backend, and stack prune for cleaning up stacks whose project directories are gone. It also drops Postgres 13 for local databases, which is a breaking change for anyone still on it. Most of the rest is bug fixes.

⚠️ Breaking changes

  • Postgres 13 is no longer supported for local databases — the CLI never shipped a Postgres 13 image, so a db.major_version = 13 config already ran Postgres 15. It is now rejected at config validation. Set db.major_version to 14, 15 or 17; 17 is the upgrade target. (#7594)

Highlights

  • supabase config validate — checks config.toml, config.json or config.jsonc on its own and reports every problem in one pass, with file, line and column. It's deterministic in CI because env() values are treated as unknown unless you pass --resolve-env. (#7553)
  • HTTPS on the local API with stack start — set [api.tls] to serve https on the API port, using the built-in cert or your own cert_path and key_path. Plain http still works for loopback. Tls on or off applies on the next stack start. macOS (Docker Desktop, Colima, Podman machine) is supported; Linux Docker and Podman fail the start check. (#7539)
  • supabase stack prune — finds and destroys local stacks whose project directory no longer exists, such as deleted worktrees. Use --dry-run to list them first, and --yes in CI or agent runs. (#7624)

New features

  • supabase config convert — rewrites config.toml as config.jsonc and removes the TOML file. It only writes if the converted file parses back to the same values. Use --dry-run to preview. Note that the JSONC file needs a CLI version that reads it; the command prints the minimum version. (#7517)
  • [local.services.<name>.container] limits — set memory (e.g. 2GiB) and cpus (e.g. 1.5) for local stack containers. Swap is disabled. Edits show as drift in stack status until you stop and start the stack. Ignored by the native runtime. (#7604)
  • [api] db_pool — sets PostgREST's local connection pool size, which is useful when tests fire many Data API calls at once. Unset keeps the current pool. It's local only and never touches a linked project. (#7584)

Improvements

  • Removed config keys now say what to use instead — for example, inbucket points to local_smtp. The error stays a hard error with exit 1. (#7593)
  • gen types --schema warns on stderr when a named schema is missing from the output, which catches typos and schemas the role can't see. Stdout and exit codes are unchanged. (#7627)
  • Plan-gate denials show the upgrade hint consistently across commands, and the telemetry event fires the same way everywhere. (#7441)
  • bootstrap prefills the directory prompt with the current directory, so a quick Enter no longer silently overwrites an existing project. Scripts and --workdir behave as before. (#7613)
  • Stack opt-in hint — when a stack-only flag like --runtime is rejected by the legacy backend, the error now tells you to set SUPABASE_EXPERIMENTAL_STACK=1 or stack = true under [experimental]. (#7592)

Bug fixes

  • Fewer macOS Keychain password prompts — bootstrap and several projects/orgs/secrets commands read the access token once per run instead of up to seven times. (#7610)
  • gen types on Postgres 14 now marks view and RETURNS TABLE columns non-null where it can infer them, matching Postgres 15+. Postgres 15+ output is unchanged. (#7599)
  • gen types return types for RETURNS TABLE functions are more accurate because the typegen dependency was bumped. (#7585)
  • supabase start no longer fails on restart when supabase/functions/.env has a multiline value such as a PEM key on Docker Desktop. (#7607)
  • supabase start is less flaky for Logflare and Vector, which now get a 60s health budget instead of 30s. (#7551)
  • supabase start, stop and rollback no longer fail with "a prune operation is already running" when several stacks share a Docker daemon. (#7550)
  • db dump and db push now pin the Supabase CA like the other db commands. (#7616)
  • Default region is no longer the private ap-east-1. (#7609)
  • Stack roles.sql runs once, as postgres — it no longer re-runs on later starts (which failed with "role already exists") or fails migrations with "permission denied for schema". (#7595)
  • Stack functions connect as postgres, not supabase_admin, so local function SQL matches deployed functions. A stack created earlier picks this up on its next stack start. (#7571)
  • stack start accepts storage analytics and vector buckets instead of refusing to start. /storage/v1/iceberg still returns 404 locally. (#7545)
  • api.tls probe reports a closed connection correctly instead of "can't reach" when the listener resets early. (#7590)

Gotchas

  • Projects with db.major_version = 13 must change it before upgrading, or they will fail validation.
  • Postgres 14 still works, but supabase start and supabase db start print a warning on every start. Postgres 14 reached end of life on November 12, 2026, and support will be removed in a later release.

Plus 2 internal improvements and dependency updates.

Full changelog: v3.1.0...v3.2.0

Don't miss a new cli release

NewReleases is sending notifications on new releases.