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.

@supabase

The open-source Firebase alternative powering thousands of startups

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

CLI FIXES FUNCTION DEPLOY FAILURES AND DB RESET 502S

By RepoJournal · Filed 06:58 UTC on August 1, 2026 · About Supabase

11 people shipped this

7ttp @7ttp 2 cited

soedirgo @soedirgo 2 cited

github-actions[bot] @github-actions[bot] 1 cited

avallete @avallete 1 cited

Miranda Limonczenko @czenko

Steven Eubank @smeubank

Ali Waseem @awaseem

Francesco Sansalvadore @fsansalvadore

Sean Oliver @seanoliver

Mats Kindahl @mkindahl

brainrake @brainrake

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].

Action items

→ Upgrade to CLI v2.111.0 before your next function deploy supabase/cli [immediate]
→ Run `supabase db reset` to confirm the Kong 502 fix if you hit it recently supabase/cli [plan]
→ Update Splinter consumers to read the new splinter.json manifest for more reliable lint selection supabase/splinter [monitor]

References

[1] v2.111.0 ↗ supabase/cli
[2] fix(cli): keep bulk function deploys going and always sync metadata (INC-699) ↗ supabase/cli
[3] fix(cli): reload kong after db reset ↗ supabase/cli
[4] fix(cli): start secrets selinux ↗ supabase/cli
[5] feat: generate splinter.json manifest and publish via release workflow ↗ supabase/splinter
[6] fix: only release on feat/fix/breaking-change commits; defer S3 upload supabase/splinter

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.

POSTGRES CHANGES NOW FILTER AND SELECT COLUMNS, CLI HARDENS SERVICE LIFECYCLE

Supabase shipped Enhancements for Postgres Changes with AND filter composition and column selection, while the CLI consolidated lazy-stack v2 with hardened OS primitives for artifact management.

javascript 81 shipped

@supabase Aug 5

CLI STABILIZES, STUDIO SHIPS MANUAL SAVES AND PRIVATELINK READ REPLICAS

Supabase cut flaky tests across the stack while rolling out editor defaults and networking features that users have been waiting for.

javascript 82 shipped

@supabase Aug 4

STUDIO REDIRECTS FIXED, DATABASE CONNECTIONS ENTER PREVIEW, PG-TOOLBELT HANDLES UTF-8

Feature preview navigation now works reliably after a nuqs timing bug fix, while database connections move into preview testing across both hosted and self-hosted deployments.

javascript 79 shipped

@supabase Aug 3

STUDIO SHIPPING SAFETY RAILS AS REALTIME HITS 2.122.0

Supabase Studio locked down form state protection across replication and OAuth flows while the Realtime service adds group lookup to its admin dashboard.

javascript 18 shipped

Elsewhere on the wire

AI Agents Aug 6

LANGCHAIN HARDENS ANTHROPIC TOOL CALLING AND GIT CREDENTIALS AS OPENHANDS SHIPS 1.10.0

LangChain fixed a critical credential leak in evaluation runs while Anthropic tool schemas get proper fallback handling, as three major agent frameworks push releases across the ecosystem.

ai-agents 54 shipped

Local LLMs Aug 6

OLLAMA FIXES KV CACHE CORRUPTION, LLAMA.CPP HARDENS FILE SEARCH, VLLM KILLS MOE LEGACY CODE

Ollama patched a critical cache corruption bug that corrupts lazy snapshots during multi-request prefills, while llama.cpp hardened Windows junction traversal and vLLM removed 14 hardcoded MoE shards across quantization methods.