RepoJournal
Supabase

@supabase

The open-source Firebase alternative powering thousands of startups

Pick a date

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

The Wire · Showcase

SUPABASE HIBERNATION WAKES ON DASHBOARD ACCESS, ETL FIXES PORT COLLISION

By RepoJournal · Filed · About Supabase

Dashboard loads now automatically wake hibernated projects, while the replicator stops crashing when ClickHouse claims port 9000.

The flagship hibernation feature gets smarter this morning [1]. Users hitting the dashboard on a suspended project no longer stare at a frozen state—the system wakes it up automatically at a central checkpoint that catches most project-ref pages. For active projects, this adds zero overhead since the ref details endpoint signals whether hibernation is active [1]. Meanwhile, the ETL replicator was crashing in local dev setups because both its Prometheus metrics listener and ClickHouse's native TCP port wanted port 9000 [2]. Default configuration now maps ClickHouse to 9001 on the host side while keeping the container internal port unchanged, killing the 'address already in use' crash loop that was breaking every developer's docker-compose startup [2]. The Realtime team also tightened broadcast warmup timing to prevent edge cases in subscription synchronization [3].

Action items

References

  1. [1] feat(hibernation): automated wake ↗ supabase/supabase
  2. [2] Move local ClickHouse native port off 9000 to avoid collision ↗ supabase/etl
  3. [3] chore: increase warmup on broadcast change ↗ supabase/realtime

FAQ

What changed in Supabase on June 15, 2026?
Dashboard loads now automatically wake hibernated projects, while the replicator stops crashing when ClickHouse claims port 9000.
What should Supabase teams do about it?
If running local ETL dev environment, update docker-compose to use CLICKHOUSE_NATIVE_PORT=9001 • Test hibernation wake flow on staging before rolling out to production • Monitor Realtime broadcast latency after warmup increase
Which Supabase repositories shipped on June 15, 2026?
supabase/supabase, supabase/etl, supabase/realtime

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.