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

PASSKEY CONFIG FIX LANDS IN CLI BETA, POSTGRES MAINTENANCE ROLLS OUT

By RepoJournal · Filed · About Supabase

Supabase CLI is fixing a critical local development gap: passkey and WebAuthn configuration now properly propagate to environment variables during `supabase start`.

The passkey config fix [1] ships in v2.103.0-beta.6 and resolves a blocker for developers testing passwordless authentication locally. This matters because WebAuthn setup has been silently broken in local environments, forcing teams to test against production config or skip that path entirely during development. The fix rolled into beta.7 alongside a Postgres image bump [2], part of a coordinated release cycle across the CLI and database layers. Meanwhile, Supabase Postgres itself shipped maintenance releases across multiple major versions: v17.6.1.132 [4], v15.14.1.132 [5], and the x86 variant [6], plus a new OrileDB experimental build [7]. The Postgres releases include test harness fixes [3] that split superuser-only operations from general test setup, reducing friction for non-root database harnesses. If you're running local development with passkey authentication, this CLI update unblocks your workflow.

Action items

References

  1. [1] fix(auth): propagate passkey config to env ↗ supabase/cli
  2. [2] fix(docker): bump supabase/postgres from 17.6.1.131 to 17.6.1.132 in /apps/cli-go/pkg/config/templates ↗ supabase/cli
  3. [3] v17.6.1.132-cli ↗ supabase/postgres
  4. [4] 17.6.1.132 ↗ supabase/postgres
  5. [5] 15.14.1.132 ↗ supabase/postgres
  6. [6] 15.14.1.132-x86 ↗ supabase/postgres
  7. [7] 17.6.0.089-orioledb ↗ supabase/postgres

FAQ

What changed in Supabase on May 31, 2026?
Supabase CLI is fixing a critical local development gap: passkey and WebAuthn configuration now properly propagate to environment variables during `supabase start`.
What should Supabase teams do about it?
Update supabase/cli to v2.103.0-beta.6+ for passkey config fix in local dev • Pull latest Postgres v17.6.1.132 or v15.14.1.132 for production databases
Which Supabase repositories shipped on May 31, 2026?
supabase/cli, 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.