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

SUPABASE SERVER RC.63 SHIPS AUTH FIX, STORAGE IMPROVES ERROR CLARITY

By RepoJournal · Filed · About Supabase

Supabase shipped server-v1.1.0-rc.63 with a critical auth fix that unblocks the JS SDK's dual-mode token handling, while storage v1.58.20 cuts through database error noise to surface the real culprits.

The server auth layer was rejecting `sb_`-prefixed tokens in user mode before falling through to secret/publishable verification [1], a breaking change for any SDK using combined auth configs. RC.63 patches this by treating `sb_` tokens as not-applicable in user mode, letting the credential chain complete [2]. That fix ships alongside a pnpm 11.1.2 bump that resolves a critical missing-time dependency bug [5]. On the storage side, v1.58.20 [4] tackles an underreported problem: schema mismatch errors were all blamed on out-of-sync migrations, when user-created triggers and RLS policies were often the real culprits [3]. The new error handling surfaces trigger/RLS details so operators can actually debug instead of chasing false positives. The main supabase/supabase repo is in refactoring mode, finishing the Tailwind v4 migration by removing @radix-ui/colors and the shadcn component suffixes [6][7][8]. Meanwhile, supavisor's upgrade test script now captures BEAM PIDs directly instead of relying on fragile pgrep calls, making test infrastructure more reliable [9].

Action items

References

  1. [1] fix(auth): skip user mode when token has sb_ prefix ↗ supabase/server
  2. [2] server-v1.1.0-rc.63 ↗ supabase/server
  3. [3] fix: improve database error messages ↗ supabase/storage
  4. [4] v1.58.20 ↗ supabase/storage
  5. [5] chore: update pnpm to 11.1.2 ↗ supabase/server
  6. [6] chore: remove shadcn suffix for `Input`, `Textarea`, `Alert` and `Collapsible` ↗ supabase/supabase
  7. [7] chore: remove `<Toggle>` `_Shadcn_` suffix (#45970) supabase/supabase
  8. [8] chore: Clean up remaining Tailwind code (#45925) supabase/supabase
  9. [9] chore: improve process management in upgrade test script (#985) supabase/supavisor

FAQ

What changed in Supabase on May 16, 2026?
Supabase shipped server-v1.1.0-rc.63 with a critical auth fix that unblocks the JS SDK's dual-mode token handling, while storage v1.58.20 cuts through database error noise to surface the real culprits.
What should Supabase teams do about it?
Deploy server-v1.1.0-rc.63 if you use combined auth modes (user + secret/publishable) • Upgrade to storage v1.58.20 to get accurate database error diagnostics in logs • Monitor main branch refactors for any broken component imports after shadcn suffix removal
Which Supabase repositories shipped on May 16, 2026?
supabase/server, supabase/storage, supabase/supabase, supabase/supavisor

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.