RepoJournal
Supabase @supabase
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-07-06
stories 10
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

SUPABASE FIXES CRITICAL PG_NET WORKER CRASH LOOP BLOCKING POSTGRES DEPLOYMENTS

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

dependabot[bot] utkarash2991 w3b6x9 imor
4 people shipped this
dependabot[bot] @dependabot[bot] 2 cited utkarash2991 @utkarash2991 1 cited w3b6x9 @w3b6x9 1 cited imor @imor 1 cited

pg_net background worker crashes once per second when a net schema exists without the extension installed, halting database operations until patched.

The pg_net team shipped an emergency fix [1] addressing a catastrophic crash loop that triggers whenever another extension (like pgsql-http) claims a net schema before pg_net installs. This is production-critical for anyone running multiple extensions on older Postgres versions. The same team also resolved macOS build failures [3] on Postgres 12-15, unblocking local development for anyone testing against legacy databases. On the docs front, Supabase clarified a high-impact misconception [2]: creating publishable and secret API keys does not revoke legacy anon and service_role keys. This ships alongside a fix [4] for an empty field bug in the log-drains config widget. The CLI landed routine dependency updates [5] and bumped golangci-lint to 9.3.0 [6] for improved linting coverage.

Action items

References

  1. [1] fix: worker crash loop when a "net" schema exists without the extension ↗ supabase/pg_net
  2. [2] docs: clarify that creating new API keys does not disable legacy keys ↗ supabase/supabase
  3. [3] build: could not build with pg versions older than 16 on macos ↗ supabase/pg_net
  4. [4] fix(docs): correct invalid variable prop on log-drains config widget (#47624) supabase/supabase ↗
  5. [5] fix(deps): bump the npm-major group across 1 directory with 5 updates ↗ supabase/cli
  6. [6] chore(ci): bump golangci/golangci-lint-action from 9.2.1 to 9.3.0 in the actions-major group ↗ supabase/cli

$ ls supabase/reviews/ # the step-back reads

the week in review CLI 2.120.0 adds persisted logs and OTel traces the month in review MCP v0.12.0 groups advisor lints, adds cost elicitation
Full archive → Weekly reviews →

Quick answers

What shipped in Supabase on July 6, 2026?
pg_net background worker crashes once per second when a net schema exists without the extension installed, halting database operations until patched. In total, 4 commits and 6 pull requests landed.
Who contributed to Supabase on July 6, 2026?
4 developers shipped this update, including utkarash2991, w3b6x9, imor, and dependabot[bot].
What were the notable Supabase updates?
fix: worker crash loop when a "net" schema exists without the extension, docs: clarify that creating new API keys does not disable legacy keys, and build: could not build with pg versions older than 16 on macos.
♥

$ log @supabase --recent

Self-hosted stack bumps realtime and storage, Studio remembers your chart range 72 shipped Realtime 2.144.0 patches a decimal CVE; realtime-csharp adds paged storage listing 151 shipped MCP server 0.14.0 adds health advisors, Supabase CLI routes every Management API call through the typed client 123 shipped Scoped OAuth reconsent in Studio, MCP drops double cost prompts 139 shipped

$ log --all # elsewhere on the wire

Alignment & Post-training verl rejects conflicting vLLM engine_kwargs, open-instruct adds MILES OPD behind a Megatron learner Interpretability nnsight 0.8.0 cuts import time from 7.6s to 1.6s

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.