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-27
stories 102

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

FIVE REALTIME RELEASES, ZERO PUBLIC BREAKING CHANGES

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

Supabase's Swift SDK quietly fixed a data-corruption bug in typed upserts while the CLI shored up its testing infrastructure, and realtime rolled through five new versions overnight.

The supabase-swift team landed a critical fix for typed upserts: a missing conflict target meant calls on keyless relations silently inserted duplicate rows, and the raw String `onConflict` could surface typos as runtime 400s [1]. They also closed the gap that prevented typed updates from setting nullable columns to NULL, forcing callers to drop to the legacy string builder [2]. These come alongside a refactor that rebuilds HTTPRuntime on swift-http-types, aligning the SDK's HTTP layer with the ecosystem [3]. Meanwhile, supabase/cli shipped v2.116.0 with fixes for piped stdin buffering, loopback proxying, and more [4], and the team sharded package-local test suites to speed up CI [5]. The supabase/postgres repo tagged five new amcheck releases across versions 15 and 17 [6][7][8], while slim-services rolled out realtime v2.130.0 and postgres 17.6.1.166 as portable artifacts [9][10].

Action items

References

  1. [1] fix(postgrest): close the typed upsert's missing conflict target ↗ supabase/supabase-swift
  2. [2] fix(postgrest): let a typed update clear a nullable column ↗ supabase/supabase-swift
  3. [3] refactor(httpruntime): build HTTPRuntime on swift-http-types ↗ supabase/supabase-swift
  4. [4] v2.116.0 ↗ supabase/cli
  5. [5] ci: shard package-local test suites (#6327) ↗ supabase/cli
  6. [6] 15.14.1.165-amcheck-2 ↗ supabase/postgres
  7. [7] 17.6.1.165-amcheck-2 ↗ supabase/postgres
  8. [8] 17.9.0.018-orioledb-amcheck-2 ↗ supabase/postgres
  9. [9] realtime v2.130.0 ↗ supabase/slim-services
  10. [10] postgres 17.6.1.166 ↗ supabase/slim-services

Quick answers

What shipped in Supabase on August 27, 2026?
Supabase's Swift SDK quietly fixed a data-corruption bug in typed upserts while the CLI shored up its testing infrastructure, and realtime rolled through five new versions overnight. In total, 43 commits, 44 pull requests, and 15 releases landed.
Who contributed to Supabase on August 27, 2026?
10 developers shipped this update, including grdsdev, github-actions[bot], Yorvi, Wendie Cheung, Pamela Chia, Pedro Rodrigues, Joshen Lim, and Julien Goux, and 2 more.
What were the notable Supabase updates?
fix(postgrest): close the typed upsert's missing conflict target, fix(postgrest): let a typed update clear a nullable column, and refactor(httpruntime): build HTTPRuntime on swift-http-types.