RepoJournal
Supabase

@supabase

The open-source Firebase alternative powering thousands of startups

Pick a date

  1. Mon 25 may
  2. Tue 26 may
  3. Wed 27 may
  4. Thu 28 may
  5. Fri 29 may
  6. Sat 30 may
  7. Sun 31 may
  8. Mon 1 jun
  9. Mon 8 jun
  10. Tue 9 jun
  11. Wed 10 jun
  12. Thu 11 jun
  13. Fri 12 jun
  14. Sat 13 jun
  15. Sun 14 jun
  16. Mon 15 jun
  17. Tue 16 jun
  18. Wed 17 jun
  19. Thu 18 jun
  20. Fri 19 jun
  21. Sat 27 jun
  22. Sun 28 jun
  23. Mon 29 jun
  24. Tue 30 jun
  25. Wed 1 jul
  26. Thu 2 jul
  27. Fri 3 jul
  28. Sat 4 jul
  29. Sun 5 jul
  30. Today 6 jul

The Wire · Showcase

SUPABASE FIXES CRITICAL PG_NET WORKER CRASH LOOP BLOCKING POSTGRES DEPLOYMENTS

By RepoJournal · Filed · About Supabase

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

FAQ

What changed 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.
What should Supabase teams do about it?
If running pg_net with other extensions, deploy the worker crash fix immediately • Review API key rotation procedures to confirm legacy keys remain valid after creating new ones • If testing pg_net on Postgres 12-15 on macOS, pull the build fix
Which Supabase repositories shipped on July 6, 2026?
supabase/pg_net, supabase/supabase, supabase/cli

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.