124 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-11
stories 75

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Postgrest v16.3 and storage v1.75.1 slim artifacts, Vitest 5 across the monorepo

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

Supabase published portable, smoke-tested runtime artifacts for postgrest v16.3 and storage v1.75.1, and moved the main monorepo to Vitest 5.0.0, which turns nested `vi.mock` calls into hard errors.

Postgrest v16.3 and storage v1.75.1 now ship as portable, smoke-tested runtime artifacts built for linux/amd64, linux/arm64, and darwin/arm64 [1][2]. Each has a multi-platform Docker image at `ghcr.io/supabase/cli/postgrest:v16.3` and `ghcr.io/supabase/cli/storage:v1.75.1`, with immutable sha256 references and an attached `SHA256SUMS` file for verifying downloaded archives [1][2].

The main supabase monorepo upgraded Vitest, `@vitest/ui`, and `@vitest/coverage-v8` from 4.1.4 to 5.0.0 [3]. The upgrade fixes what v5 turned into hard errors: `vi.mock` calls inside `beforeAll`, `beforeEach`, or test bodies had to move to module scope, affecting the Studio and docs setup files plus four Studio tests, and the `vi.clearAllMocks()` boilerplate was dropped where v5's `clearMocks` default makes it redundant [3]. The dbdev website followed with a Dependabot bump of `@vitest/mocker` from 4.1.0 to 5.0.0 [4].

dbdev also bumped its `next` dependency from 16.2.11 to 16.3.3 in the /website directory, a release the source says contains security fixes for listed advisories including a critical one [5]. Separately, a dbdev CI test-coverage failure was fixed [6].

On the docs and evals desks: the Supabase docs sidebar now renders a semantic list hierarchy instead of putting `li` elements directly under the root `ul` [7], and a follow-up extracts shared `NavSection` composition components (`NavSectionCaret`, `NavSectionContent`, `NavSectionList`) used by both the guide and reference navs [8]. A new regression eval covers `@supabase/middleware`, with the scorer driving an API-key gate through the local gateway (no key and wrong key both 401, right key 200) and checking `Vary: Origin` as the CORS signal [9].

Action items

References

  1. [1] postgrest v16.3 ↗ supabase/slim-services
  2. [2] storage v1.75.1 ↗ supabase/slim-services
  3. [3] chore(deps): upgrade vitest to v5 ↗ supabase/supabase
  4. [4] chore(deps): bump @vitest/mocker from 4.1.0 to 5.0.0 in /website in the npm_and_yarn group across 0 directory ↗ supabase/dbdev
  5. [5] chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates ↗ supabase/dbdev
  6. [6] fix: failing test coverage in CI ↗ supabase/dbdev
  7. [7] fix(docs): guides sidebar a11y elements ↗ supabase/supabase
  8. [8] fix(docs): guide nav collapsible parity ↗ supabase/supabase
  9. [9] feat: add @supabase/middleware regression eval ↗ supabase/evals

Quick answers

What shipped in Supabase on September 11, 2026?
Supabase published portable, smoke-tested runtime artifacts for postgrest v16.3 and storage v1.75.1, and moved the main monorepo to Vitest 5.0.0, which turns nested `vi.mock` calls into hard errors. In total, 35 commits, 34 pull requests, and 6 releases landed.
Who contributed to Supabase on September 11, 2026?
10 developers shipped this update, including github-actions[bot], SaxonF, alaister, jeremenichelli, antlio, supabase-evals-releaser, mandarini, and supabase-evals-releaser[bot], and 2 more.
What were the notable Supabase updates?
postgrest v16.3, storage v1.75.1, and chore(deps): upgrade vitest to v5.