Supabase edge function returns 401 "Invalid JWT" after switching to the new API keys: the safe fixEdge functions return 401 Invalid JWT after moving to sb_publishable keys? Here's the fix, plus the step that keeps your function from going public.4 min read·getshipready.hashnode.dev53m ago
@supabase/server adapters are removed on December 1: migrate without making your endpoints publicHono, H3, Elysia, NestJS adapters in @supabase/server go away 1 Dec 2026. withClaims instead of withRequiredClaims turns a 401 into a 200. Safe swap.3 min read·getshipready.hashnode.dev5h ago
Supabase is retiring the eyJ keys: the safe migrationThe 10-minute swap to publishable/secret keys, and the one mistake that puts your secret key in the public bundle.4 min read·getshipready.hashnode.dev20h ago
Supabase 42501 "permission denied for table" after the Oct 30 change: the safe fixYour app worked yesterday. You (or your AI tool) added a new table, and now every request to it fails with 42501. Nothing is broken. Supabase changed a default, and the fix takes one minute. But the f4 min read·getshipready.hashnode.dev1d ago