151 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-08
stories 54

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

POSTGRES SHIPS FRESH BUILDS ACROSS THREE VERSIONS, SUPABASE STUDIO HARDENS SCOPED TOKEN CONTROLS

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

Supabase postgres cut four releases overnight spanning versions 15, 17, and 17 with OrientDB, while Studio rolled out lifecycle-aware token expiration and alternative permission modeling across the platform.

The postgres desk shipped a flurry of releases [1] [2] [3] [4], with v17.6.1.160-cli addressing cron trigger permissions and a multigres data directory override bug [3]. Over on supabase/supabase, the Studio team landed three interconnected token security features: lifecycle and role-aware scoped token view sheet [5], enforced expiration date limits with configurable boundaries [6], and alternative permission modeling to support OR-of-AND access patterns [7]. These three PRs work together to give engineers finer control over short-lived credential grants. Meanwhile, evals refreshed eval results twice from automated runs [9] [10], and etl migrated replicator error emails from the legacy pipeline-error endpoint to the new ETL email API, preserving error deduplication in the process [8]. The broader story here: token security is getting substantially more granular, and infrastructure plumbing is shifting to centralized email routing.

Action items

References

  1. [1] 15.14.1.160 ↗ supabase/postgres
  2. [2] 17.9.0.013-orioledb ↗ supabase/postgres
  3. [3] v17.6.1.160-cli ↗ supabase/postgres
  4. [4] 17.6.1.160 ↗ supabase/postgres
  5. [5] feat(studio): lifecycle and role-aware scoped token view sheet (#48848) ↗ supabase/supabase
  6. [6] feat(studio): enforce expiry scoped pat (#48811) ↗ supabase/supabase
  7. [7] fix(studio): model scoped pat permissions as OR-of-AND alternatives - smaller version ↗ supabase/supabase
  8. [8] feat(replicator): migrate error emails to ETL email API ↗ supabase/etl
  9. [9] chore: refresh eval results ↗ supabase/evals
  10. [10] chore: refresh eval results ↗ supabase/evals

Quick answers

What shipped in Supabase on August 8, 2026?
Supabase postgres cut four releases overnight spanning versions 15, 17, and 17 with OrientDB, while Studio rolled out lifecycle-aware token expiration and alternative permission modeling across the platform. In total, 23 commits, 23 pull requests, and 8 releases landed.
Who contributed to Supabase on August 8, 2026?
10 developers shipped this update, including supabase-evals-releaser, claude[bot], claude, supabase-evals-releaser[bot], Manuel Mendez, github-actions[bot], kemal.earth, and Miranda Limonczenko, and 2 more.
What were the notable Supabase updates?
15.14.1.160, 17.9.0.013-orioledb, and v17.6.1.160-cli.