RepoJournal
Supabase

@supabase

The open-source Firebase alternative powering thousands of startups

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

One email a day. Unsubscribe in one click.

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

SUPABASE LOCKS DOWN LEGAL DOCS AND POSTGRES BUILD PIPELINE

By RepoJournal · Filed · About Supabase

Three new legal agreement versions ship across the marketing site while the evals framework tightens postgres best-practices detection and realtime patches a hot-path performance leak.

The main marketing push this cycle centers on legal infrastructure: Enterprise SaaS Subscription Agreement v3 [1], Terms of Service v3 effective August 1, 2026 [2], and a unified refactor of the legal page shells [3] that standardizes versioning across all agreements. These are live on the production site now. In parallel, supabase/evals tuned the `supabase-postgres-best-practices` evaluator [4] to activate more reliably on postgres-heavy scenarios, verified against claude-code-sonnet-5 and codex-gpt-5.4-mini in local testing. The evals repo also added Apache 2.0 licensing [5] to align with other Supabase repositories. Realtime shipped v2.121.3 [6] with a critical hot-path fix: "on a hot-path it's important to not re-query the DB" [7]. The ETL pipeline cleaned up impossible states in its core worker spawn logic [8], removing unnecessary error handling that couldn't actually fail. Security also got a refresh: vulnerable dependencies across the main supabase repo were bumped [9] including Next.js and PostCSS updates. Postgres released six new builds across versions 15 and 17, including a fresh 17.9.0 with OrileDB support [10]. The engineering org landed 42 commits and 41 PRs across 5 repositories with 11 releases total.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] feat(www): add Enterprise SaaS Subscription Agreement v3 ↗ supabase/supabase
  2. [2] feat(www): add Terms of Service v3 (effective August 1, 2026) ↗ supabase/supabase
  3. [3] refactor(www): unify legal page shells and versioning ↗ supabase/supabase
  4. [4] Tune supabase-postgres-best-practices activation ↗ supabase/evals
  5. [5] add `LICENSE` ↗ supabase/evals
  6. [6] v2.121.3 ↗ supabase/realtime
  7. [7] fix: cache not found feature flags ↗ supabase/realtime
  8. [8] ref(core): remove impossible state ↗ supabase/etl
  9. [9] chore: Bump vulnerable deps ↗ supabase/supabase
  10. [10] 17.9.0.15799999-orioledb ↗ supabase/postgres

Quick answers

What shipped in Supabase on July 31, 2026?
Three new legal agreement versions ship across the marketing site while the evals framework tightens postgres best-practices detection and realtime patches a hot-path performance leak. In total, 42 commits, 41 pull requests, and 11 releases landed.
Who contributed to Supabase on July 31, 2026?
11 developers shipped this update, including Pedro Rodrigues, mattrossman, supabase-evals-releaser, ivasilov, claude, SaxonF, github-actions[bot], and iambriccardo, and 3 more.
What were the notable Supabase updates?
feat(www): add Enterprise SaaS Subscription Agreement v3, feat(www): add Terms of Service v3 (effective August 1, 2026), and refactor(www): unify legal page shells and versioning.

More from @supabase

Daily updates, in your inbox

Follow Supabase

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

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?