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-15
stories 30

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

CLI UNLOCKS ORIOLEDB PROJECTS, EVALS MOVES TO VERCEL SANDBOXES

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

Supabase CLI now exposes the experimental flags needed to spin up OrioleDB managed projects, while the evals system abandons GitHub Actions for faster, sandboxed test execution.

The CLI's `projects create` command now accepts `--postgres-engine 17-oriole` to provision OrioleDB instances directly, ending the workaround of manual API calls [1]. This lands alongside two quality-of-life fixes: the update notifier can now be silenced with `SUPABASE_NO_UPDATE_NOTIFIER` [2], and Windows developers finally get working `migration new` that doesn't lose files to tmpfs vanishing [3]. Docker Snap users also got relief; secrets now stream as tar archives instead of failing when the host's `/tmp` is invisible to the container [4]. On the evals front, the bigger shift is architectural: test execution moved from GitHub Actions to Vercel Sandboxes with p-limit and p-retry for concurrency [6], while the Row Level Security eval was retooled to actually measure whether reading the guide produces secure policies, not just recite it [5]. A parser fix ensures claude-code tool calls match Codex behavior for scoring consistency [7].

Action items

References

  1. [1] feat(cli): add experimental --release-channel and --postgres-engine flags to projects create (CLI-2180) (#6186) ↗ supabase/cli
  2. [2] feat(cli): suppress update notifier (CLI-1922) ↗ supabase/cli
  3. [3] fix(cli): persist new migrations on Windows (CLI-2183) ↗ supabase/cli
  4. [4] fix(cli): stream container secrets (CLI-2190) ↗ supabase/cli
  5. [5] feat: eval the Row Level Security guide in supabase.com/docs (#168) ↗ supabase/evals
  6. [6] feat: move eval execution from GitHub Actions to Vercel Sandboxes ↗ supabase/evals
  7. [7] fix(core): normalize claude-code MCP tool names to bare endpoint ↗ supabase/evals

Quick answers

What shipped in Supabase on August 15, 2026?
Supabase CLI now exposes the experimental flags needed to spin up OrioleDB managed projects, while the evals system abandons GitHub Actions for faster, sandboxed test execution. In total, 11 commits, 12 pull requests, and 7 releases landed.
Who contributed to Supabase on August 15, 2026?
7 developers shipped this update, including Andrew Valleteau, 7ttp, jgoux, Miranda Limonczenko, supabase-evals-releaser, mattrossman, and Rodriguespn.
What were the notable Supabase updates?
feat(cli): add experimental --release-channel and --postgres-engine flags to projects create (CLI-2180) (#6186), feat(cli): suppress update notifier (CLI-1922), and fix(cli): persist new migrations on Windows (CLI-2183).