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-09-27
stories 2

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Supabase evals refreshed from the latest automated run

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

The evals desk published a new set of results, and that is the entire wire: nothing else moved in the last 24 hours.

chore: refresh eval results supabase/evals

by supabase-evals-releaser

The automated releaser rewrote apps/web/src/data/eval-results.json from the latest eval run, so the numbers the evals site renders now match the most recent run rather than the previous snapshot. No code paths changed; the diff is data.

chore: refresh eval results (#341) supabase/evals

by supabase-evals-releaser[bot]

The same refresh landed as a commit, co-authored by mattrossman, carrying the identical eval-results.json update that the pull request introduced. If you consume the file directly rather than through the site, the commit is where the new values became permanent.

Quick answers

What shipped in Supabase on September 27, 2026?
The evals desk published a new set of results, and that is the entire wire: nothing else moved in the last 24 hours. In total, 1 commits and 1 pull requests landed.
Who contributed to Supabase on September 27, 2026?
2 developers shipped this update, including supabase-evals-releaser and supabase-evals-releaser[bot].
What were the notable Supabase updates?
chore: refresh eval results and chore: refresh eval results (#341).