124 wires and counting

$ follow Supabase

Keep up with Supabase in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-01
stories 73

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

CLI FIXES FUNCTION DEPLOY FAILURES AND DB RESET 502S

By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology

Supabase CLI v2.111.0 ships fault-tolerant function deployments and fixes the Kong gateway going dark after database resets, while Splinter adds structured lint manifests for downstream consumers.

Bulk function deployments were failing catastrophically: a single upload error during `functions deploy` would abort before syncing metadata to the backend, leaving the remote in a stale state and every subsequent deploy broken [2]. v2.111.0 makes deployments fault-tolerant, continuing even if individual functions fail and always syncing metadata at the end [1]. Separately, `supabase db reset` was leaving the Kong gateway returning 502s forever because Kong cached the old container IPs of auth/storage/realtime and never re-resolved them [3]. The fix runs `kong reload` after the satellite restarts, the same pattern `functions serve` uses, so the gateway picks up the moved containers without downtime. CLI also fixed SELinux failures on Fedora with rootless Podman where bind mounts needed explicit relabeling [4]. On the Splinter side, the linter now emits a structured `splinter.json` manifest alongside the monolithic SQL blob, letting downstream consumers like the platform advisor select and filter lints by reading JSON fields instead of parsing with regexes and paren-depth scanners [5]. The release workflow gates on release-worthy commits (feat/fix/breaking-change only; chore/docs/test no longer trigger) and publishes to GitHub Releases [6].

Quick answers

What shipped in Supabase on August 1, 2026?
Supabase CLI v2.111.0 ships fault-tolerant function deployments and fixes the Kong gateway going dark after database resets, while Splinter adds structured lint manifests for downstream consumers. In total, 33 commits, 35 pull requests, and 5 releases landed.
Who contributed to Supabase on August 1, 2026?
11 developers shipped this update, including github-actions[bot], 7ttp, avallete, soedirgo, Miranda Limonczenko, Steven Eubank, Ali Waseem, and Francesco Sansalvadore, and 3 more.
What were the notable Supabase updates?
v2.111.0, fix(cli): keep bulk function deploys going and always sync metadata (INC-699), and fix(cli): reload kong after db reset.