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 FIXES 90K DAILY BOT 404S, TANSTACK-DB CATCHES UP TO 0.6.X

By RepoJournal · Filed · About Supabase

LLM bots have been hammering your docs guides with 404s on pages that work fine for humans, and it's fixed.

The docs middleware was blindly rewriting all `/docs/guides/*` requests to the markdown handler without checking whether a `.md` file actually existed [1]. That meant ~90K daily 404s landed on real HTML pages serving 200 responses to regular traffic, poisoning bot crawls while your content stayed live. The fix catches both the middleware and the handler, so bots now get what humans get [2]. Over in tanstack-db, the 0.6.x version bump broke the whole package: @tanstack/db widened the `From` type to include `UnionFrom` and `UnionAll`, but `serializeFrom()` still only accepted the old union, causing type-check failures [4]. That's now fixed with proper union serialization support [5]. The CLI picked up a minor runtime patch addressing a regression in parameter validation [3]. Postgres continues shipping test builds across versions 15, 17.6, and 17.9 with OrioleDB variants [6][7][8][9][10].

Action items

References

  1. [1] fix(docs): stop named-bot markdown 404s on guides ↗ supabase/supabase
  2. [2] fix(docs): stop named-bot markdown 404s on guides (#47337) supabase/supabase
  3. [3] chore(deps): bump github.com/oapi-codegen/runtime from 1.4.1 to 1.4.2 in /apps/cli-go in the go-minor group across 1 directory ↗ supabase/cli
  4. [4] fix: support @tanstack/db 0.6.x `From` union types ↗ supabase/tanstack-db
  5. [5] fix: support @tanstack/db 0.6.x `From` union types (#6) supabase/tanstack-db
  6. [6] 17.9.0.001-orioledb-orioledb-test-4 ↗ supabase/postgres
  7. [7] 15.14.1.140-orioledb-test-4 ↗ supabase/postgres
  8. [8] 17.6.1.140-orioledb-test-4 ↗ supabase/postgres
  9. [9] 17.6.1.140-orioledb-test-4-x86 ↗ supabase/postgres
  10. [10] 15.14.1.140-orioledb-test-4-x86 ↗ supabase/postgres

FAQ

What changed in Supabase on June 28, 2026?
LLM bots have been hammering your docs guides with 404s on pages that work fine for humans, and it's fixed.
What should Supabase teams do about it?
Deploy docs fix to stop the 90K daily 404s hitting your guides • Upgrade tanstack-db to catch the union type fix if you're on 0.6.x • Update CLI to pick up the oapi-codegen runtime patch
Which Supabase repositories shipped on June 28, 2026?
supabase/supabase, supabase/cli, supabase/tanstack-db, supabase/postgres

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.