[renovate]

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
supabase (source)	2.101.0 → 2.122.0
supabase (source)	2.101.0 → 2.122.0

---

Release Notes

supabase/cli (supabase)

v2.122.0

Compare Source

Supabase CLI v2.122.0 — 2026-10-23

This release is mostly fixes. The headline changes are supabase/supabase.lock for pinning stack service versions, PGSSL* and TLS settings now reaching db push --linked and pg_dump, and clearer config parse errors. Several fixes cover start/stop on Podman and stack reliability.

Highlights

• Pin stack service versions in a lock file — stack mode can run any published service version, match your hosted project after supabase link, and reproduce the whole local stack from a committed supabase/supabase.lock. (#​7195)
• Postgres TLS settings now apply to db push --linked and pg_dump — PGSSLMODE, PGSSLROOTCERT, and PGSSLCERT/PGSSLKEY are read from your shell on direct connections, and remote db dump and the first db pull pass the resolved TLS settings through. Before, verify-full was ignored and client-cert servers rejected the dump. (#​7261, #​7266)

New features

• supabase --help shows token permissions — every command's help now has a PERMISSIONS section listing the personal access token permissions it needs, so you can scope tokens for CI without guessing. (#​7268)
• supabase stack can run any published service version — the lock file (see Highlights) also lets you try a hotfix or match production versions. (#​7195)

Improvements

• Config errors say what's wrong and where — start, status, stop, and functions serve used to print a bare CliConfigParseError. They now point to the bad line. inf and nan numbers are rejected at load time instead of slipping through. (#​7267)
• Heads-up: the default target is changing — the CLI now warns before the upcoming switch to a local default target. Check your scripts if you rely on the current default. (#​7186)
• db pull and pg_dump honor TLS config — see Highlights. (#​7266)

Bug fixes

• supabase start and stop no longer fail every few runs on Podman — when there's no docker on PATH (macOS with podman machine), you no longer hit failed to inspect docker image or ssh: handshake failed: EOF. (#​7270)
• supabase stop --no-backup no longer exits 1 with older Docker CLIs — it works with Docker CLI older than 23.0 talking to a newer daemon. (#​7177)
• Piping CLI output into head or another reader that exits early exits cleanly — the CLI used to crash with Unknown: Stdio.stdout (exit 1), and with --output json it could hang forever. It now exits 0. (#​7175)
• db diff --from linked --to linked no longer fails without a database password — it used to fail with password authentication failed for user "cli_login_postgres" when no password was set via --password, SUPABASE_DB_PASSWORD, or supabase/.env. (#​7139)
• functions deploy --use-api uploads multiline dynamic imports — functions with import( split across lines, or with import attributes, no longer throw Module not found after deploy. (#​7282)
• supabase init test OTP example works — the [auth.sms.test_otp] example now includes the country code, so +14152127777 gets the test code instead of sending a real SMS. (#​7279)
• Stack: concurrent native stacks no longer share a backend port — two stacks started at once could bind Logflare to the same private port. (#​7184)
• Stack: idle gateway connections stay open for 75 s — a short pause between API calls no longer ends in TypeError: fetch failed. (#​7193)
• Stack: local Studio logs work again — analytics is pinned to Logflare 1.50.15, so logs pages no longer show "Backend error". (#​7182)
• Stack: rest starts when a db_pre_request hook rejects requests without an app header — it used to hang on readiness. (#​7216)
• Stack: native launches are more reliable — the launcher waits for a cache lock instead of failing, and Realtime waits for its own bind line before it's marked ready. (#​7145)

Internal

Plus 6 internal improvements and dependency updates.

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

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

v2.120.0

Compare Source

Supabase CLI v2.120.0 — 2026-10-06

A mix of usability improvements and bug fixes, with two major additions for debugging and observability: service logs now persist to disk and ship to Analytics, and CLI runs can export OpenTelemetry traces for end-to-end performance analysis. Stack commands also accept short IDs from stack list, making them much less tedious to use.

Highlights

• Service logs persist, ship to Analytics, and stack logs gains history — Every service's output now lives in <stateRoot>/<stackId>/logs/, survives restarts and owner exits, and reaches your project's Logs page in Studio. supabase stack logs prints retained history by default; -f/--follow switches to live output. New --since, --tail, and --service flags. (#​6893)
• Trace CLI runs end-to-end with opt-in OTLP export — Set SUPABASE_TRACE_FILE to export a JSON trace of one run to a file, or SUPABASE_OTLP_ENDPOINT to stream to Tempo, Jaeger, or Grafana. Spans track migrations, containers, API operations, and database queries. Off by default; costs nothing when unset. Two scripts (trace-report, bench-cli) turn traces into critical-path analysis and fair A/B comparisons. (#​6935)
• Stack commands now accept short IDs — supabase stack list prints an 8-character ID; every --stack-id flag now accepts it (or any unique 4+ character prefix), eliminating the tedium of copying full 64-character hashes. (#​6967)

Improvements

• Upgrade check is now cached outside projects — supabase --version and commands run outside a supabase/ directory no longer hit GitHub's API on every run; the check is cached in ~/.supabase/cli-latest for 10 hours. On slow or offline networks, this saves ~3 seconds per run. (#​6939)
• Config rejection errors name the setting and the fix — When a saved stack rejects a configuration change, the error now says which config.toml key or env var changed and suggests reverting it or running supabase stack destroy --stack-id <id>. JSON and stream-json errors carry structured details for agents. (#​6944)
• Command telemetry now tags stack backend and OrioleDB — Telemetry records whether each command ran on legacy or stack backend, the runtime (docker, podman, or native), and whether the project uses OrioleDB. (#​6940)

Bug fixes

• Config: stop treating disabled data API as enabled — config diff, config push, and config pull no longer report false drift or propose incorrect changes when the data API is disabled. (#​6949)
• Gateway URLs now print even when API is disabled — supabase start now shows API_URL, FUNCTIONS_URL, and MCP_URL regardless of [api] enabled, since Kong serves auth regardless. (#​6986)
• Typegen stdin feed no longer hangs on early-exit tools — Fixed an intermittent hang in supabase gen types when a tool exits before reading its full input. (#​6948)
• stop --no-backup now prunes migra cache — Volumes created by db diff and db pull are now labeled and cleaned up on stop --no-backup, not left behind. (#​6982)
• Native stack: wait for processes to exit before reporting stopped — supabase stack stop now confirms that native service processes have exited before returning, preventing port conflicts or file locks when services restart. (#​6937)
• Native stack: prevent ephemeral port collisions on reopen — Backend ports are now reserved below the OS ephemeral range, fixing intermittent port already in use errors when stacks restart. (#​6941)
• Fix intermittent instance root claim race — Instance root owner markers are now written atomically, eliminating a rare concurrency bug on high-load systems. (#​6933)

Dependency updates

• @​supabase/typegen 0.2.2 — TypeScript output now includes a ComputedFields key on tables and views, fixing type generation for functions with named row parameters. (#​6919)
• pg-delta 1.0.0-alpha.57 — No longer emits unnecessary REVOKE statements for column-level grants when running declarative sync against unchanged exports. (#​7020)

---

Plus 1 internal improvement.

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

v2.119.0

Compare Source

Supabase CLI v2.119.0 — 2026-09-30

This release delivers stability improvements for local development with 30+ fixes focused on Docker container management, networking, and connection handling. Key fixes address Docker Desktop compatibility on macOS and Windows, session persistence, and request routing. OrioleDB configuration graduates from experimental to stable.

Highlights

• Storage uploads fixed on Docker Desktop for macOS — Resumable uploads and S3 endpoints now work through the gateway. (#​6921)
• Stack connection details visible on start — Database URL, MCP endpoint, and other connection info show immediately after launch for easier debugging. (#​6894)
• OrioleDB configuration is now stable — Move from experimental_oriole to standard oriole config. (#​6828)

New features

• Type generation languages from registry — gen types automatically picks up new language targets as Supabase adds them. (#​6822)
• Studio MCP server at /mcp — Serve Studio's Model Context Protocol server for AI agent and third-party tool integration. (#​6898)
• Edge function testing improvements — New testing entrypoint and Promise-based API. (#​6841)

Improvements

• Docker preferred over Podman for automatic runtime selection. (#​6859)
• Containers named by project and service for visibility. (#​6867, #​6870)
• Studio stays active 5 minutes after last request. (#​6866)
• Function deno.json files loaded as Deno configuration. (#​6907)

Bug fixes

• Storage and network connectivity on Docker Desktop (macOS and Windows). (#​6921, #​6887)
• Stacks clean up when Docker is unavailable. (#​6825)
• Migra session settings persist through database reconnects. (#​6884)
• Local functions read request bodies before responding. (#​6830)
• Escape sequences in quoted strings no longer split incorrectly. (#​6906)
• Yes/no prompts reject unrecognized answers. (#​6910)
• Database socket connections require authentication. (#​6833)
• Postgres containers stop cleanly. (#​6834)
• Upstream connections reused across proxied requests. (#​6925)
• Image pulls retry on transient registry failures. (#​6879)
• Mailpit database isolated per stack. (#​6901)
• SMS provider configuration handled when unset. (#​6685)

---

Plus internal improvements and dependency updates.

Full changelog: supabase/cli@v2.118.0...v2.119.0

v2.118.0

Compare Source

This release introduces new workflow commands (pull, notebooks, whoami), experimental stack management commands, and fixes numerous stability issues across the CLI and stack runtime.

Highlights

• New supabase pull command — orchestrates a complete local setup from your remote project. (#​6526)
• Experimental stack management commands — stack start, stop, status, list, logs, prepare, restart for controlling your local development stack. (#​6506, #​6507, #​6508, #​6592, #​6593, #​6601, #​6603)
• Generate types natively against your selected stack — gen types runs without Docker setup, using the stack you've configured. (#​6652)

New features

• New utility commands: whoami for your current account and notebooks push/notebooks pull for syncing notebooks. (#​6552, #​6598, #​6599)
• Storage commands target managed stack — local storage operations work directly against your development stack. (#​6633)
• Compute command overhaul — replaced experimental workers with gated compute new, compute build, etc. (#​6554)
• Experimental stack via environment — set SUPABASE_EXPERIMENTAL_STACK=true in supabase init. (#​6665)
• Build context exclusions — specify exclude patterns to skip files from compute builds. (#​6658)
• Stack management operations — new commands for status, logs, prepare, and destroy workflows. (#​6576)
• API client updates: v2 notebook endpoints and pg-delta 1.0.0-alpha.52. (#​6595, #​6632)

Improvements

• Faster stack initialization: Independent services start concurrently; snapshots copied in one command; PostgreSQL reused for storage helper tasks. (#​6809, #​6709, #​6700, #​6760)
• Better stack diagnostics: Service startup failures show recent output; explicit lifecycle states; automatic retry on rate-limited image pulls. (#​6791, #​6613, #​6778)
• Realtime networking: Connections use IPv4 instead of hostname for improved compatibility. (#​6777)

Bug fixes

• Startup stability:

  • macOS CLI no longer hangs during state publication. (#​6783)
  • Docker daemon stalls won't block db start. (#​6530)
  • Large SQL blocks no longer stall db reset. (#​6697)

• Consent and safety:

  • storage rm now requires explicit confirmation. (#​6683)
  • Config push and seeding consent properly honored. (#​6670, #​6647)
  • Piped config pull input handled correctly. (#​6589)

• Configuration and paths:

  • Content paths enforced within project root. (#​6498)
  • Explicit --workdir no longer climbs to parent projects. (#​6497)
  • Local authentication overrides honored. (#​6523)
  • Environment variable overrides and encrypted secrets resolved. (#​6535)
  • Only verifying SSL modes treated as local TLS demand. (#​6664)

• Docker diagnostics:

  • Out-of-memory container kills properly classified from logs. (#​6714)
  • Edge runtime kills reported instead of lost streams. (#​6615)
  • Function serve state accurately reflects container reality. (#​6594)

• API client and HTTP:

  • Deep object query parameters expanded into per-key pairs. (#​6596)
  • HTTP resources scoped to client lifetime. (#​6627)
  • projects create won't resend on dropped connections. (#​6704)
  • Management API client synced with current spec. (#​6519)

• Functions and compute:

  • Function requests no longer cloned unnecessarily. (#​6580)
  • Bodyless function requests retry on worker retirements. (#​6759)
  • Failed compute new scaffolds roll back cleanly. (#​6805)
  • Compute logs correctly filtered on subservice attribute. (#​6578)

• Stack services: Schemas provisioned on db reset; service images validated; full resource cleanup; Functions bootstrap config anchored; error reporting accurate. (#​6763, #​6797, #​6701, #​6776, #​6573, #​6623, #​6628, #​6563, #​6801)

---

Plus N internal improvements and dependency updates.

Full changelog: supabase/cli@v2.117.0...v2.118.0

v2.117.0

Compare Source

Supabase CLI v2.117.0 — 2026-09-07

This release debuts experimental Workers commands for Edge Function management, introduces config management commands (diff and pull), and publishes the @​supabase/config package to npm for programmatic config access. The release also includes performance improvements, bug fixes across auth and database sync, and infrastructure updates.

Highlights

• Supabase Workers suite (experimental) — Manage Edge Functions from the CLI with new supabase experimental workers subcommands: new, list, status, delete, push (with --no-wait to skip build wait), and logs. Includes exposure control and instance configuration. (#​6261, #​6262, #​6263, #​6349, #​6371, #​6389, #​6410, #​6432)

• Config management suite — supabase config diff shows what would change before pushing; supabase config pull fetches your remote configuration locally. Config push now applies changes as diffs and confirms branch targets upfront. (#​6295, #​6438, #​6446, #​6454)

• @​supabase/config npm package — Programmatic access to config validation and diffing logic. (#​6423, #​6339, #​6366, #​6447)

New features

• Function slug in served functions — Function slugs are now available as environment variables. (#​6345)

• Slim Docker images — Set SUPABASE_USE_SLIM_IMAGES=true to use smaller GHCR images locally. (#​6382)

• Shadow baseline cache opt-out — Caching is now on by default; add --no-cache-baseline to disable. (#​6403)

• Bundled pg-delta as standard — The bundled pg-delta engine is now the only implementation. (#​6487)

Improvements

• SUPABASE_API_* environment variable overrides now work. (#​6467)

• PowerShell users see a warning if the shell corrupts piped database dumps. (#​6418)

• Parallel provisioning speeds up pg-delta schema diffs. (#​6215)

• Unified output across workers commands. (#​6389)

• ProjectConfig now covers hosted-field configuration. (#​6451)

Bug fixes

• CLI accepts sbp_v0 tokens. (#​6360)

• Auth email content_path restricted to project root. (#​6489)

• Extension-managed database objects properly deleted in declarative sync. (#​6449)

• Colliding schema names no longer skipped. (#​6394)

• Provisioned ledger DDL statements now skipped. (#​6422)

---

Plus multiple dependency updates and internal improvements.

Full changelog: supabase/cli@v2.116.0...v2.117.0

v2.116.0

Compare Source

Supabase CLI v2.116.0 — 2026-08-26

This release speeds up your local dev and adds workers support to your config. Major wins: supabase start/stop are much faster, migration testing is quicker, and edge runtime output streams in real time.

Highlights

• supabase start and stop are 10 seconds faster — Docker shutdown no longer waits; saves time on every restart. (#​6203)
• Migration testing is faster with shadow database baseline caching — Your baseline is cached as a PGDATA snapshot, speeding up repeated diffs and migrations. (#​6184)
• Edge runtime bootstrap streams output in real time — See progress instead of waiting for full completion. (#​6273)
• New [workers] configuration section — Configure workers in supabase/config.toml. (#​6260)

Improvements

• auto_expose_new_tables defaults to true — Matches your Supabase project behavior by default. (#​6337)

Bug fixes

• Piped stdin is no longer buffered endlessly — Fixed memory overflow when piping data to the CLI. (#​6290)
• Stale database connections are detected and dropped — Operations no longer hang on dead connections. (#​6277)
• Edge runtime respects system file descriptor limits — Prevents "too many open files" crashes. (#​6284)
• DROP INDEX CONCURRENTLY works outside migrations — Index drops no longer deadlock your transaction. (#​6276)
• Postgres role management is more stable — Roles are restored correctly after changes. (#​6246)
• Loopback network proxying is bypassed — Local requests route directly, improving reliability. (#​6283)
• Kong local DNS cache is optimized — DNS resolution is more responsive and consistent. (#​6324)
• Service startup is more reliable — Fixed edge cases during start and stop. (#​6245)

---

Plus 14 internal improvements and dependency updates.

Full changelog: supabase/cli@v2.115.0...v2.116.0

v2.115.0

Compare Source

Supabase CLI v2.115.0 — 2026-08-18

This release changes two defaults you should know about before upgrading CI: schema diffing now uses the bundled pg-delta engine, and supabase test db fails when it finds zero tests. It also makes migrations faster and more consistent, and fixes supabase start on confined Docker installs.

⚠️ Breaking changes

• Schema diffing defaults to the bundled pg-delta engine — db diff, db pull, and declarative schema generate/sync now use the in-process pg-delta engine instead of the legacy implementation. Generated SQL and transaction-aware file splits can differ from previous output, and there is no automatic fallback — coverage gaps warn, and --strict-coverage makes them fatal. The declarative schema directory also defaults to supabase/schemas now, matching the legacy engine; if your tree lives under the old supabase/database default, move it or set declarative_schema_path = "./database" under [experimental.pgdelta] in supabase/config.toml. If the new engine blocks you, set SUPABASE_USE_PG_DELTA_NEXT=false to unblock yourself and open a GitHub issue describing what broke — the opt-out is temporary and will be removed in about a month. (#​6102)
• supabase test db now fails when no tests run — a run where pg_prove finds zero pgTAP tests exits non-zero with no pgTAP tests found in <paths> instead of reporting success. Previously a typo'd path, an empty tests directory, or a bind-mount mismatch could leave CI green while testing nothing. If a pipeline legitimately runs zero tests, drop the supabase test db step. (#​6210)
• --password now beats SUPABASE_DB_PASSWORD on db remote — db remote changes|commit prefer an explicit --password over the environment variable; previously the env var silently won due to a flag-binding bug. If your automation sets both, the flag value is now the one used. (#​6162)

Highlights

• Faster, more consistent migrations — db reset and db push batch migration and seed statements again, cutting runs from minutes to seconds on Windows; migration list, db pull, and migration repair order migrations by version like db push, so an in-sync tree no longer shows phantom conflicts; and migration new writes the file before reporting success on Windows. (#​6224, #​6225, #​6192)
• Link a preview branch directly — supabase link accepts a project ref, or the name or UUID of a branch of the currently linked project, both as the positional argument and via --project-ref. (#​6168)
• Clearer errors — functions serve setup failures name the actual filesystem problem instead of An error occurred in Effect.tryPromise; a crashed db diff --use-migra run fails loudly instead of printing "No schema changes found"; and an unreachable database during batched migrations reports as a connection error. (#​6191, #​6240, #​6234)

New features

• Per-function env files in functions serve — standalone supabase functions serve discovers supabase/functions/<slug>/.env for each function, alongside the shared supabase/functions/.env; --env-file overrides both. supabase start does not load these files. (#​6182)
• Experimental projects create flags — --release-channel and --postgres-engine pick the release channel and Postgres engine for new projects. Both require --experimental and stay hidden from --help while in preview. (#​6186)
• Silence the update notice — set SUPABASE_NO_UPDATE_NOTIFIER=1 to suppress the new-version notice printed after commands. (#​6143)

Improvements

• supabase start polls booting services one at a time again, matching the Go CLI — concurrent health checks could burst Docker subprocesses and exhaust retries on constrained machines. (#​6149)
• Piped text output respects backpressure instead of buffering in memory, so supabase db dump | <slow consumer> no longer risks running out of memory on large databases. (#​6212)
• The bundled Go binary only includes the commands still proxied to it, shrinking the installed size. (#​6162)

Bug fixes

• supabase start works with strictly confined Docker installs (such as Docker Snap) and remote Docker contexts: container secrets stream over stdin via docker cp instead of being staged as plaintext files in /tmp. (#​6201)
• supabase functions serve <name> accepts its optional function-name argument again; the command still serves all discovered functions, matching the Go CLI. (#​6173)
• Auth email template and notification content_path values resolve against the project root consistently. (#​6160)

---

Plus 12 internal improvements and dependency updates.

Full changelog: supabase/cli@v2.114.0...v2.115.0

v2.114.0

Compare Source

Supabase CLI v2.114.0 — 2026-08-12

This release ports several database and function commands from Go to native TypeScript, fixes crashes in the functions importer, and improves startup resilience. Local database connections are now more robust, and you have more control over synchronization and stack state.

Bug fixes

• Functions import-scanner no longer crashes when encountering non-directory entries (#​6164)
• Local database connections now retry on transient failures (#​6137)
• Redundant Docker network creation during startup is skipped (#​6130)

New features

• --project-ref flag — Specify your project explicitly for commands that need it (#​6156)
• Skip vault sync — New option to skip vault synchronization (#​6131)
• Managed stack persistence — Stacks now persist across restarts (#​6152)

TypeScript port progress

• Now served by the TypeScript shell: db diff, db reset, functions download, migration squash. Behavior matches the Go CLI. (#​6150, #​6062, #​6082, #​6151, #​6027)

---

Plus 5 internal improvements and dependency updates.

Full changelog: supabase/cli@v2.113.0...v2.114.0

v2.113.0

Compare Source

Supabase CLI v2.113.0 — 2026-08-08

This release improves error reporting and continues the TypeScript migration. The CLI now properly surfaces serve staging errors and handles timestamps with timezone offsets.

Bug fixes

• supabase serve now displays staging errors instead of suppressing them (#​6113)
• API calls now accept timestamps with timezone offsets (#​6117)

TypeScript port progress

• Now served by the TypeScript shell: db reset, gen bearer-jwt, shell completion. Behavior matches the Go CLI. (#​6026, #​6064, #​6083)

---

Plus 1 internal dependency update.

Full changelog: supabase/cli@v2.112.0...v2.113.0

v2.112.0

Compare Source

Supabase CLI v2.112.0 — 2026-08-07

This release fixes migration ordering, stops supabase start from hanging when analytics migrations fail, and unblocks Edge Functions deploys on Windows. There is one breaking change for private npm registry users.

⚠️ Breaking changes

• functions deploy no longer forwards NPM_AUTH_TOKEN into Docker bundling — this restores Go CLI behavior. If you deploy against a private npm registry with an .npmrc that expands ${NPM_AUTH_TOKEN}, Docker-based bundling will fail to authenticate after upgrading. Inline the token in .npmrc, or deploy with supabase functions deploy --use-api. (#​6005)

Highlights

• Migrations run in version order — db push and migration up no longer report an already-applied migration as missing when one version is a string prefix of another (for example 1 vs 10, or 20260420 vs 20260420010000). (#​6038)
• supabase start no longer hangs when analytics migrations fail — the analytics container now exits and retries instead of booting against an unmigrated database. If your stack is already stuck, run supabase stop && supabase start once after upgrading; the fix only takes effect when the container is recreated. (#​6093)
• Edge Functions deploys work on Windows again — bundling no longer fails with permission errors. (#​6109)

Improvements

• supabase start works on SELinux-enforcing hosts (for example Fedora with rootless Podman) — CLI-generated secret files are relabeled so containers can read them. (#​6000)
• functions serve and Docker-based deploys continue when the working directory can't be mounted. (#​6048)

Bug fixes

• Malformed --profile config fails fast with a clear error instead of being silently ignored. (#​6095)
• -o toml/yaml/json machine-readable output matches the Go CLI again. (#​6002)
• functions download can no longer write files outside supabase/functions via path traversal in downloaded entry paths. (#​5956)
• supabase start reuses existing volumes instead of failing when they already exist, notably on Podman. (#​6037)
• Kong reloads after supabase db reset, so auth requests no longer fail with 502 when container IPs rotate. (#​6017)
• Custom auth email templates no longer revert to defaults after db reset, functions serve reloads, or branch switch. (#​6065)
• SSO provider schemas are synchronized — OIDC and SAML definitions match API expectations. (#​6058)
• db schema declarative generate prints your configured declarative directory as written in config instead of an absolute path. (#​6066)
• Small parity fixes from the July audit — db dump, db query formatting, credentials handling, and other edge cases now match the Go CLI. (#​5978)

Deprecations

• db diff --use-pg-schema is deprecated — plan to remove it from your workflows. (#​6060)
• db pull --experimental is deprecated — use db pull --declarative for per-object schema files instead. (#​6028)

TypeScript port progress

• Now served by the TypeScript shell: db start container bootstrap, db test, and bootstrap's db push step. Behavior matches the Go CLI. (#​6022, #​6063, #​6021)

---

Plus 33 internal improvements and dependency updates.

Full changelog: supabase/cli@v2.111.0...v2.112.0

v2.111.0

Compare Source

Supabase CLI v2.111.0 — July 31, 2026

This release focuses on reliability, output clarity, and Go CLI compatibility. Key improvements include better error messages, resilient function deployments, and clearer database workflows. Plan upgrade hints help guide feature adoption.

Highlights

• Function deployments are fault-tolerant — bulk function deploys continue even if individual functions fail; metadata always syncs. (#​6018)
• Database workflows clearer — db pull shows "Connecting..." status and proper relative paths; sync bootstrap confirms schema was written. (#​5968, #​5971)
• Proactive plan upgrade hints — CLI suggests plan upgrades when your current plan limits what you're trying next. (#​5943)

Improvements

• Error messages now match Go CLI — database operations, migrations, connections, and initialization show the same helpful context and formatting for easier troubleshooting (#​5967, #​5969, #​5976, #​5977, #​5979, #​5948)
• Configuration rendering — SMS/MFA and SSO templates display as formatted output instead of raw escape sequences; SSO PUT requests include domain fields (#​5944, #​5973)
• Network feature gating — experimental features (vanity subdomains, network restrictions) properly gated to avoid surprises (#​5945)
• Docker and database updates — PostgreSQL upgraded to 17.6.1.156 with PUBLIC privilege revoke fix; unrunnable images diagnosed clearly (#​5970, #​5966, #​5899, #​5983, #​5962)

Bug fixes

• --yes and SUPABASE_YES honored consistently across all confirmation prompts (#​5947)
• --debug mode now preserves TLS, keeping connections secure during local development (#​5981)
• Comma-separated flag values now parse correctly for network-related flags (#​5975)
• Unnecessary debug hints no longer shown when confirmation prompts are declined (#​5946)
• --db-url respects SSL mode for secured connections (#​5980)
• pg-delta selinux bind mount issue fixed (#​5990)

---

Plus minor improvements and dependency updates.

Full changelog: supabase/cli@v2.110.0...v2.111.0

v2.110.0

Compare Source

Supabase CLI v2.110.0 — 2026-07-27

Core database commands are now on the native TypeScript shell, with fixes for Edge Function bundling, type generation, and local stack recovery. Most of this release is quality improvements and stability fixes.

Highlights

• Recover your local stack from interruptions — supabase start can now recover a stopped database instead of requiring a clean restart. (#​5953)

Improvements

• Edge Function bundling works again — Docker-based bundling restored for Edge Functions. (#​5875)
• Type generation without config.toml — supabase gen types now works even without supabase/config.toml. (#​5881)
• Storage seeding skips OS junk files — macOS .DS_Store and similar files no longer clutter seeded buckets. (#​5938)
• Better error messages — Removed redundant "Expected" prefixes and aligned formatting with Go CLI. (#​5831, #​5804, #​5832)
• Functions deploy validates --jobs — Invalid job counts are caught early. (#​5797)
• Telemetry resilience — No more hangs when endpoints are blocked. (#​5880)
• API keys redacted in output — Credentials no longer appear in error messages. (#​5891)

Bug fixes

• Local migrations no longer sync to remote projects via db push. (#​5951)
• db pull works correctly with per-connection role step-down and pg-delta. ([#​5895](https://redirect.github.com/sup

[!IMPORTANT]
✂ PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 these updates again.

---

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

---

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