[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
supabase (source)	2.120.0 → 2.121.0

---

Release Notes

supabase/cli (supabase)

v2.121.0

Compare Source

Supabase CLI v2.121.0 — 2026-10-14

This release is mostly stack reliability fixes, plus new stack options and deprecation warnings you'll want to see before the next major version. Most entries below are from PR titles, not full PR review.

Highlights

• OrioleDB through db.orioledb_version — set the OrioleDB version in config instead of relying on a separate setup path. (#​6934)
• Repeatable --stack-id in stack destroy — tear down several stacks in one command. (#​6964, #​7000)
• Gateway requests show up in Studio — API Gateway logs in Studio now include requests that pass through the local stack gateway. (#​6942)

New features

• stack destroy --stack-id accepts multiple IDs — e.g. supabase stack destroy --stack-id a --stack-id b. (#​6964, #​7000)
• Leftover containers from deleted stacks get cleaned up — stale containers are removed automatically instead of piling up. (#​7017)
• Changed endpoint ports apply on restart — if you change endpoint ports while a stack is stopped, the new ports are used the next time it starts. (#​6950)
• Deprecation warnings for db pull and domains flags — you now see a warning at runtime when you use a deprecated flag. (#​7115)

Improvements

• functions serve defaults to stream-json for agents — when running non-interactively, output is streamed as JSON so agent tooling can parse it. (#​7027)
• Heads-up: deprecated config, env vars and import maps will be removed in the next major version — the CLI now warns when you use them. Migrate before upgrading to that major. (#​7154)
• Clearer db remote commit and inspect db deprecation messages — the warnings now say the features are removed in the next major version. (#​7108)
• More specific failure telemetry — stack and platform failures are classified and named more precisely, which makes issues easier to triage. (#​7044, #​7113, #​7137, #​7067)

Bug fixes

• supabase start works with Podman when no snippets are present. (#​7089)
• Stack creates the supabase_functions database on the stack backend. (#​7029)
• functions serve overrides apply after the stack has started. (#​7028)
• Native Postgres trusts your host CA bundle, so connections through corporate or custom certificates work. (#​7023)
• Auth database and stack host connections stay alive instead of dropping mid-session. (#​7080)
• Gateway writes no longer fail under load, because they reuse keep-alive connections. (#​7075, #​6981)
• Containers whose host port was taken before start are recreated rather than failing to start. (#​7081)
• Database helpers are removed when their owner exits, so they stop leaking between runs. (#​7014, #​6962)
• Running dependents restart when a prerequisite crashes, so the stack recovers without a manual restart. (#​7093)
• pg_cron jobs run in background workers on native Postgres. (#​7039)
• Database helpers are created by name before they're attached to. (#​7068)
• supabase stop waits for a concurrent Docker prune instead of failing. (#​7143, #​7129)
• Config accepts the new Management API Postgres settings, so they no longer get rejected. (#​7056, #​7054, #​6934)

---

Plus 1 internal improvement and dependency update.

Full changelog: supabase/cli@v2.120.0...v2.121.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.