npm supabase 2.117.0-beta.16
v2.117.0-beta.16

latest release: 2.117.0-beta.17
3 hours ago

2.117.0-beta.16 (2026-09-04)

Bug Fixes

  • cli-go: repoint overlay.yaml at renamed JitListAccessResponse schema (#6425) (f50e083), closes #6417 #6423
  • cli: skip provisioned ledger ddl (CLI-2275) (#6422) (08103c0)
  • cli: warn when PowerShell mangles piped dumps (#6418) (430d5ed)
  • config: align pgdelta format_options example with the 180 default (#6435) (adbbe16), closes #6434 #6434
  • deps: bump the go-minor group across 1 directory with 2 updates (#6442) (c326986)
  • deps: bump the go-minor group across 2 directories with 2 updates (#6458) (81a1f81)
  • deps: bump the go-minor group across 2 directories with 3 updates (#6429) (d345d94)
  • deps: bump the npm-major group across 1 directory with 28 updates (#6430) (44f463a)

Continuous Integration

  • config: add independent release automation for @supabase/config (CLI-2233) (#6381) (ed81a1c), closes #6366 #6366

Features

BREAKING CHANGES

  • config: outside packages/config/ must not produce a major —
    plus merge-commit, root-commit (--root), and non-ASCII-path (-z vs
    core.quotePath) edges.
  • The plan refuses to run without a baseline config-v* tag: with none,
    semantic-release would cut 1.0.0 with notes generated from the entire
    monorepo history — a whole-history changelog as the approval artifact.
    Escape hatch: CONFIG_RELEASE_ALLOW_NO_BASELINE=1.
  • While private: true (until CLI-2169 flips it), the plan job still
    runs everything — version, gate, pack — and reports
    blocked_on_private; every config push to develop rehearses the plan
    half of the train while publishing nothing.

Don't miss a new supabase release

NewReleases is sending notifications on new releases.