Supabase APIDeprecationhigh
Supabase removes @supabase/server framework adapters on Dec 1, 2026
- Detected
- Oct 6, 2026
- Effective
- Dec 1, 2026(in 15 days)
- Confidence
- 97%
What changed
The four framework adapters in @supabase/server (/adapters/hono, /adapters/h3, /adapters/elysia, /adapters/nestjs) are deprecated and will be removed on December 1, 2026. Developers must migrate to a framework-specific bridge file that wraps @supabase/middleware entries.
What to do
Copy the appropriate bridge file for your framework (Hono, H3, Elysia, NestJS, or TanStack Start) from the Supabase frameworks guide into your project. Add @supabase/middleware as a direct dependency, replace adapter registrations with bridge calls (e.g., toHono([withRequiredClaims(), withSupabaseClient()])), and update call sites from nested supabaseContext to flat keys like c.var.supabase and c.var.jwtClaims.
Affected
param: @supabase/server/adapters/honoparam: @supabase/server/adapters/h3param: @supabase/server/adapters/elysiaparam: @supabase/server/adapters/nestjsSource: supabase.com (Supabase's own page, checked by Breakwatch)
Is your code affected?
Search your repositories for the Supabase SDK and the names above:
Or let Breakwatch do it: connect a repo and see which files call Supabase, then get the next change as an alert pointing at those files. Check a repo free
Put it in your calendar: Supabase deadlines (.ics) or every vendor's.