Deprecation notice: @supabase/supabase-js will require TypeScript 5.0+#

Summary#

Starting with a minor release on or after January 2027, @supabase/supabase-js and the packages it bundles (postgrest-js, auth-js, realtime-js, storage-js, functions-js) will require TypeScript 5.0 or later. TypeScript 4.7–4.9 will no longer be tested or supported.

Consistent with our existing Support Policy, raising the minimum TypeScript version ships in a minor release and is not considered a breaking change, the same way we handle end-of-life Node.js versions.

Why#

• Our type declarations currently target a TypeScript 4.7 floor (May 2022, ~4 years old) — roughly a dozen releases and two major lines behind current TypeScript.
• Holding the 4.7 floor blocks us from using modern type features that materially improve the SDK's types — const type parameters, the satisfies operator, and (later) NoInfer for the postgrest-js query-builder generics.
• It also pins transitive tooling (e.g. zod) to older releases.

What you need to do#

• On TypeScript 5.0 or newer: nothing. You're already covered.
• On TypeScript 4.7–4.9: upgrade your project's TypeScript to >= 5.0 before the release above. TypeScript 5.x has been stable since March 2023.

Timeline#

• Now: advance notice (this post); our SDKs continues to emit 4.7-compatible types.
• On/after January 2027: a minor release raises the floor to TypeScript 5.0. The last version supporting TypeScript 4.7 will be called out in the release notes and the README once that release is cut.

Questions and concerns welcome below.

Here's everything that happened with Supabase in the last month:

OpenCode integrates with Supabase#

OpenCode connects your agent to your Supabase database, Edge Functions, and logs. It configures the MCP setup for you.

Read the blog →

TanStack DB syncs with Supabase#

@supabase-labs/tanstack-db syncs TanStack DB collections with your Supabase tables over PostgREST and Realtime. It's available in alpha.

Watch the demo →

Wrappers adds a MongoDB foreign data wrapper#

Wrappers v0.6.2 lets you query and join MongoDB collections directly from Postgres. It also fixes OpenAPI FDW pagination.

Read the docs →

Multigres supports LISTEN/NOTIFY across pooled connections#

Multigres keeps Postgres LISTEN/NOTIFY working even when connections are pooled away from clients.

Read the blog →

Realtime Broadcast supports binary payloads#

Realtime Broadcast now sends and receives binary payloads in addition to JSON. Binary payloads cut encoding overhead for cases like sensor telemetry and live screenshot streaming.

The Dart, Kotlin, and Python clients don't support binary payloads yet, and older SDK versions silently drop them. Update your client before you rely on it.

Read the docs →

Quick Product Announcements#

• Postgres log_connections now defaults to off for new projects on all tiers as of July 9, and existing Free and Pro projects are being migrated to the new default. [GitHub Discussion]
• pg_graphql v1.6.2 ships with GraphQL schema introspection off by default, so enable it per schema if you use GraphiQL or codegen tools. [GitHub Discussion]
• Audit Log Drains are available, so you can stream your project's audit logs to an external destination. [Docs]
• Connect copies every environment variable @supabase/server needs in a single click. [Demo]
• Self-hosted Docker defaults changed: API_EXTERNAL_URL now includes the /auth/v1 prefix, and the default image moves to Postgres 17. [GitHub Discussion]

Meet the Supabase team#

• Supabase Live: Building high quality Supabase apps using TRAE. July 22 at 7 pm PT. [Register]
• Supabase x Claude Community Meetup in Dublin. [Register]
• Hangout with the Supabase team during Casual Wednesdays on Discord at 10:00 am PT. [Join]

Made with Supabase#

• Shapeships: A multiplayer browser game using simultaneous-turn mechanics, built on an authoritative Supabase backend. [Website]
• Blind OS: An autonomous outreach and client-management system that finds leads, qualifies them, and follows up on payments. [Website]
• rlsautotest: Generates pgTAP tests and seed data from your Supabase RLS policies to prove, per table and identity, who can read or write which rows. [GitHub] [PyPI]
• Heym: An open-source visual AI workflow automation platform with a native Supabase node for querying and mutating tables through PostgREST. [GitHub]

Community Highlights#

• A practical security checklist for non-technical builders, with Row Level Security flagged as the single most important fix. [Read]
• A transparent cost breakdown for a personal life-management system built with Claude Code and Supabase, plus an honest look at the security tradeoffs of self-hosting your own data. [Read]
• A widely-shared guide to vibecoding with Claude Code positions Supabase as the default data layer and login system in its standard setup flow. [Read]

We are changing the default value of the Postgres log_connections setting from on to off for new projects, and will be migrating all Free and Pro projects to the new default configuration. This reduces log volume and noise, and aligns with industry-standard defaults (RDS, GCP Cloud SQL also default to off). We will be exposing this configuration to all users via dashboard and API for better log management, with log_connnections and log_disconnections now available via the Update postgres config API route and will take effect from 9 July onwards.

Who's affected#

• New projects (all tiers) created after 9 July will have log_connections=off by default.
• Existing Teams + Enterprise customers (including HIPAA add-on customers) - Configuration is unchanged
• Existing Free / Pro customers - log_connections will be turned off from 9 July. This configuration can be re-enabled below

How to re-enable#

You can re-enable log_connections via the dashboard under Database > Settings. It can also be re-enabled programmatically via the Management API via the Update postgres config API route. Changes will only take effect from 9 July onwards.

Learn more about PostgreSQL logging settings in our logging documentation.