RepoJournal
Supabase

@supabase

The open-source Firebase alternative powering thousands of startups

Pick a date

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

The Wire · Showcase

DOCS SCHEMA FIX KILLS 230 SEARCH CONSOLE ERRORS, POSTGRES WRAPPERS ACROSS VERSIONS

By RepoJournal · Filed · About Supabase

Supabase eliminated critical Google Search Console errors plaguing the docs, while shipping five Postgres builds across 15, 17, and architecture variants.

The docs team crushed a phantom Google Search Console blocker that was flagging 230 `/docs/guides/*` pages for missing `item` fields in BreadcrumbList schemas [1]. The fix filters out intermediate nav nodes without URLs, bringing the schema into compliance with Google's structured data spec—a silent win that recovers organic visibility. Meanwhile, monorepo sprawl got a small mercy: the auto-generated `rss.xml` will stop ghosting your git status in `apps/www` [2], eliminating the phantom modified file that's bitten every contributor at least once. On the Postgres front, the team shipped builds across three release lines—Postgres 15.14.1 and 17.6.0/17.6.1 with wrappers support [3][4][5]—plus x86-specific variants [6][7] for broader hardware compatibility. Realtime and multiplayer.dev both landed supabase-js v2.105.4 [8], which hardens auth JSON parsing, restores abort detection in PostgREST, and guards sessionStorage access in restricted-storage browsers [9].

Action items

References

  1. [1] fix(docs): always emit BreadcrumbList `item` field ↗ supabase/supabase
  2. [2] chore(www): stop tracking auto-generated rss.xml ↗ supabase/supabase
  3. [3] 15.14.1.122-wrappers ↗ supabase/postgres
  4. [4] 17.6.0.079-orioledb-wrappers ↗ supabase/postgres
  5. [5] 17.6.1.122-wrappers ↗ supabase/postgres
  6. [6] 17.6.0.079-orioledb-wrappers-x86 ↗ supabase/postgres
  7. [7] 15.14.1.122-wrappers-x86 ↗ supabase/postgres
  8. [8] chore: update @supabase/supabase-js to v2.105.4 ↗ supabase/realtime
  9. [9] chore: update @supabase/supabase-js to v2.105.4 ↗ supabase/multiplayer.dev

FAQ

What changed in Supabase on May 11, 2026?
Supabase eliminated critical Google Search Console errors plaguing the docs, while shipping five Postgres builds across 15, 17, and architecture variants.
What should Supabase teams do about it?
Clear your git status and pull latest from main — rss.xml will stop appearing as modified • Test your Realtime client connections with supabase-js v2.105.4 — sessionStorage guards matter for some browsers • Plan Postgres upgrade if you're on older 17.6.0 builds — 17.6.1 wrappers available now
Which Supabase repositories shipped on May 11, 2026?
supabase/supabase, supabase/postgres, supabase/realtime, supabase/multiplayer.dev

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.