---
title: "Ship-Ready (@getshipready) | Hashnode"
description: "Ship-Ready (@getshipready) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@getshipready"
---

@getshipready

# Ship-Ready

@getshipready · Joined November 2026

### [Supabase edge function returns 401 "Invalid JWT" after switching to the new API keys: the safe fix](https://getshipready.hashnode.dev/supabase-edge-function-returns-401-invalid-jwt-after-switching-to-the-new-api-keys-the-safe-fix?utm_source=hashnode&utm_medium=feed)

Edge 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.dev](https://getshipready.hashnode.dev/supabase-edge-function-returns-401-invalid-jwt-after-switching-to-the-new-api-keys-the-safe-fix?utm_source=hashnode&utm_medium=feed)

[1h ago](https://hashnode.com/posts/supabase-edge-function-returns-401-invalid-jwt-after-switching-to-the-new-api-keys-the-safe-fix/6afe68efac45526259c93dcc)

### [@supabase/server adapters are removed on December 1: migrate without making your endpoints public](https://getshipready.hashnode.dev/supabase-server-adapters-are-removed-on-december-1-migrate-without-making-your-endpoints-public?utm_source=hashnode&utm_medium=feed)

Hono, 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.dev](https://getshipready.hashnode.dev/supabase-server-adapters-are-removed-on-december-1-migrate-without-making-your-endpoints-public?utm_source=hashnode&utm_medium=feed)

[6h ago](https://hashnode.com/posts/supabase-server-adapters-are-removed-on-december-1-migrate-without-making-your-endpoints-public/6afe22b4eca60870f8929fa3)

### [Supabase is retiring the eyJ keys: the safe migration](https://getshipready.hashnode.dev/supabase-is-retiring-the-eyj-keys-the-safe-migration?utm_source=hashnode&utm_medium=feed)

The 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.dev](https://getshipready.hashnode.dev/supabase-is-retiring-the-eyj-keys-the-safe-migration?utm_source=hashnode&utm_medium=feed)

[21h ago](https://hashnode.com/posts/supabase-is-retiring-the-eyj-keys-the-safe-migration/6afd503ee5bff178c3245a6f)

### [Supabase 42501 "permission denied for table" after the Oct 30 change: the safe fix](https://getshipready.hashnode.dev/supabase-42501-permission-denied-for-table-after-the-oct-30-change-the-safe-fix?utm_source=hashnode&utm_medium=feed)

Your 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 f

4 min read · [getshipready.hashnode.dev](https://getshipready.hashnode.dev/supabase-42501-permission-denied-for-table-after-the-oct-30-change-the-safe-fix?utm_source=hashnode&utm_medium=feed)

[1d ago](https://hashnode.com/posts/supabase-42501-permission-denied-for-table-after-the-oct-30-change-the-safe-fix/6afd07665bd692e12b89c5f4)
