New updates and product improvements
The privileged metrics endpoint could intermittently panic while serving concurrent requests, because a single parser instance was shared across those requests instead of each request getting its own. The panic stopped metrics collection for the affected project until the metrics service restarted.
Each request now gets its own parser instance, so concurrent metrics requests no longer interfere with each other.
The logs.all Management API endpoint is being removed on 23rd September 2026 (Wednesday), two months from this announcement. Log querying moves to a new ClickHouse-backed logs endpoint. The new endpoint accepts ClickHouse SQL only. It returns every source through a single unified logs table instead of a separate table per source.
You are impacted only if you query the logs.all Management API endpoint (.../analytics/endpoints/logs.all). This includes any scripts, integrations, or tooling that call it directly.
If you do not call this endpoint, no action is needed. Using logs through the dashboard Logs Explorer is not affected.
analytics/endpoints/logs.all to analytics/endpoints/logs.source_name instead of selecting a source table. All sources now live in one logs table. Filter to a specific source in the WHERE clause.Before (query a source table directly):
_10SELECT timestamp, event_message_10FROM edge_logs_10ORDER BY timestamp DESC_10LIMIT 100
After (filter the unified stream by source_name):
_10SELECT timestamp, event_message_10FROM logs_10WHERE source_name = 'edge_logs'_10ORDER BY timestamp DESC_10LIMIT 100
Any query that previously targeted a specific table must now add a source_name filter in its WHERE clause.
Nested fields move from the metadata array to a flat log_attributes map. Before, you added one CROSS JOIN unnest() per level of nesting to reach a field. Now you read the field directly from log_attributes with map key access. The joins go away.
Before (unnest each level of metadata):
_10SELECT timestamp, request.method, header.x_real_ip_10FROM edge_logs_10CROSS JOIN unnest(metadata) AS m_10CROSS JOIN unnest(m.request) AS request_10CROSS JOIN unnest(request.headers) AS header
After (read from the log_attributes map):
_10SELECT_10 timestamp,_10 log_attributes['request.method'] AS method,_10 log_attributes['request.headers.x_real_ip'] AS x_real_ip_10FROM logs_10WHERE source_name = 'edge_logs'
| Date | Change |
|---|---|
| 23 July 2026 | Changelog published |
| 23 September 2026 | logs.all endpoint removed for all projects |
logs endpoint and its parametersStarting 2026-08-05, specifying an explicit version when creating or updating a Postgres extension on Supabase is deprecated. Statements like:
_10create extension pgvector version '0.7.0';_10alter extension pg_graphql update to '1.5.9';
will still succeed, but the requested version is now ignored: the extension is installed at (or updated to) its current default version on your project's Postgres instance, and the statement emits a warning:
_10WARNING: only superusers can specify extension versions, ignoring version "0.7.0" and installing the default version
In a future release, announced separately in advance, these statements will be rejected with an error instead.
Supabase instances ship multiple versions of some extensions side by side. Allowing any role to install or downgrade to an older version means projects can end up running extension versions with known security issues — including reintroducing vulnerabilities that were already patched in the default version. Pinning versions is now reserved for platform operations.
create extension / alter extension ... update without a version clause.pg_dump output never includes version clauses).Stream Postgres changes to BigQuery in near real time with Supabase Pipelines, a managed CDC service configured right in the Dashboard. Now in public alpha on all paid plans.
Self-hosted Supabase makes Envoy the default API gateway, replacing Kong, the week of 2026-08-09. Opt back into Kong if you rely on its HTTPS listener, a custom kong.yml, or the kong service name.
Supabase now blocks all changes to the realtime schema: creating, altering, or dropping objects fails with a permission error. RLS policies on realtime.messages still work.
@supabase/supabase-js will require TypeScript 5.0 starting January 31, 2027, dropping support for TypeScript 4.7 to 4.9. Upgrade to 5.0 or later before then.
Supabase Developer Update for July 2026: Realtime Broadcast now supports binary payloads, Wrappers v0.6.2 adds a MongoDB foreign data wrapper, and OpenCode integrates with Supabase.
Postgres log_connections defaults to off for new projects and existing Free and Pro projects from 2026-07-09, cutting log noise. Re-enable it via the dashboard or Management API.
Self-hosted Supabase's default API_EXTERNAL_URL now includes /auth/v1 from the week of 2026-07-06. SAML SSO users must repoint their IdP to the new /auth/v1/sso/saml/* endpoints.
Supabase Realtime Broadcast now sends and receives binary payloads (bytea) over WebSockets, the REST API, and the database, cutting JSON overhead for sensor streams and image frames.
Supabase's June developer update: $500M Series F led by GIC, Auth passkeys in beta, the Supabase ChatGPT app, the Supabase plugin for AI coding agents, and Multigres 0.1 alpha released.
From 2026-06-03, new Free plan projects using Supabase's default SMTP cannot customize auth email templates. Existing projects keep theirs. Configure a custom SMTP provider to customize.
Supabase Auth now supports passkeys (Beta): passwordless, phishing-resistant sign-in built on WebAuthn using biometrics, a device PIN, or a hardware security key. No action required.
pg_graphql 1.6.0 disables GraphQL introspection by default for new projects created on or after 2026-06-29. Re-enable it by adding a comment on the schema.
Supabase project owners and admins can grant temporary database access via Personal Access Tokens (Feature Preview), scoped by role with expiry up to 90 days. No password disclosure.
Self-hosted Supabase makes analytics and vector opt-in on 2026-06-03. Logs Explorer users must include docker-compose.logs.yml in their docker compose invocation.
Self-hosted Supabase switches Studio and postgres-meta from supabase_admin to postgres on 2026-06-17. Existing instances must run utils/reassign-owner.sh to migrate ownership in public.
Self-hosted Supabase's default db image moves from Postgres 15 to Postgres 17 on 2026-06-17. PG 15 data does not auto-upgrade; run the upgrade script, or pin supabase/postgres:15.x to stay.
Supabase support for Postgres 14 ends on 2026-07-01. Projects still on Postgres 14 will be upgraded automatically; projects using removed extensions (timescaledb, plv8, pgjwt) will be paused.
Supabase client libraries (supabase-js, auth-js, realtime-js, functions-js, storage-js, postgrest-js) drop Node.js 20 support on 2026-06-30. Upgrade to Node.js 22 or later before that date.
Supabase's May developer update: custom OAuth/OIDC providers for Auth, ISO 27001 certification, @supabase/server SDK, branching without Git by default, plus Data API auto-exposure changes.
Supabase's OAuth token endpoint /v1/oauth/token returns HTTP 200 instead of 201 starting 1 June 2026. Check for any 2XX status (response.ok), not a hardcoded 201.
New tables in the public schema will no longer be exposed to the Supabase Data API by default. Opt-in today, default for new projects on 2026-05-30, enforced on all projects on 2026-10-30.
The Supabase Dashboard adds an RLS Tester (Feature Preview): run SELECT queries as any role, see which RLS policies fire, and debug policies. Enable it from your profile menu.
Supabase client libraries (supabase-js, swift, flutter, py) now automatically retry GET and HEAD requests to PostgREST on transient 520, 503, and network errors. Enabled by default, opt-out per call.
Supabase will add applicable taxes (VAT, GST, sales tax) to invoices based on each organization's billing address, rolling out from 1 May to 30 June 2026. Review your billing address and Tax ID.
The Supabase CLI now ships pg-delta (Public Alpha): a Postgres 15+ schema diffing engine and declarative SQL workflow. Edit .sql files, run supabase db schema declarative sync.
Supabase's April developer update: GitHub integration on all plans, Multigres Operator open-sourced, Supabase joins the Stripe Projects developer preview, and Supabase docs available over SSH.
Supabase Edge Functions now rate-limit recursive and nested function-to-function calls at a minimum of 5,000 requests per minute per chain. Inbound and external requests are unaffected.
Supabase's March developer update: Log Drains on Pro, Storage performance and security overhaul, docs export as Markdown for AI tools, and Edge Functions dashboard for self-hosted and CLI.
The Supabase Data API stops returning the OpenAPI spec to anon-key requests on 11 March 2026 for new projects and 8 April 2026 for all projects. Use a service role or secret API key instead.
Supabase's February developer update: PrivateLink GA, Supabase as an official Claude connector, Postgres best practices for AI agents, and a heads-up that pg_graphql is becoming opt-in.
The Supabase Table Editor now batches inserts, edits, and deletes into a single transaction with a diff preview. Enable it under Feature Previews > Queue table operations.
pg_graphql will be disabled by default on new Supabase projects, and on existing projects older than 30 days with zero GraphQL traffic. Re-enable it via Database Extensions if needed.
Saving SQL snippets now works in local Studio via the CLI. Snippets are stored in supabase/snippets, ready to commit alongside your code. Requires CLI v2.72.7 or later.
Supabase's January developer update: Stripe Sync Engine integration in the Dashboard, Index Advisor in the Table Editor, PostgREST v14 on the Data API, and the 2026 security roadmap.
The Data API is upgrading to PostgREST v14 worldwide, starting in ap-northeast-1. GET throughput rises ~20% via a JWT cache, and schema cache loading is faster. No breaking changes.
Developer Update for December 2025: Supabase ETL, Analytics and Vector Buckets, iceberg-js, Supabase Platform, OAuth 2.1 provider, Kiro integration, and AWS Marketplace listing.
Supabase Vector Buckets (Public Alpha) can now be managed from the dashboard. Store, index, and query vector embeddings at scale alongside your project's other storage.
Dashboard updates for 10 Nov to 25 Nov 2025: refreshed Storage UI ahead of Analytics and Vector buckets, and per-template toggles for the new security-sensitive Auth emails.
Supabase Auth adds email templates for security-sensitive account changes: password, email, phone, identity link or unlink, and MFA enrollment. Enable via Feature previews.
Supabase Analytics Buckets (Public Alpha) can now be managed from the dashboard. Store large datasets for analytics and reporting alongside your project's other storage.
Dashboard updates for 20 Oct to 3 Nov 2025: refreshed Storage UI ahead of new bucket types, split Auth Reports, Sentry Log Drains support, and three new Realtime configuration settings.
supabase-js 2.75.1 and CLI 2.53.1+ infer SETOF functions as embedded relationships in .select() queries and raise compile-time errors for invalid rpc calls. Regenerate types to adopt.
Dashboard updates for 6 Oct to 20 Oct 2025: a faster Auth Users page with URL-persisted search, model switching for the Assistant, and a max events per second setting for Realtime.
The Supabase MCP server is now hosted at https://mcp.supabase.com/mcp. Connect via browser-based OAuth 2 from clients like ChatGPT, no npx or personal access token required.
New projects on Postgres 17.6.1.016 and later ship pgmq 1.5.1, which changes delay parameter behavior. Upgrades for existing projects are paused until an upstream fix lands.
Dashboard updates for 22 Sep to 6 Oct 2025: Assistant response speed and quality improvements, contextual error handling in the Table Editor, and a wrap on Supabase Select.
The Supabase JS client libraries (supabase-js, auth-js, postgrest-js, realtime-js, storage-js, functions-js) now live in a single monorepo. No action required for package users.
Dashboard updates for 8 Sep to 22 Sep 2025: Query Performance Advisor refinements and a new Auth Audit Logs setting to stop writing audit logs to the project database.
Data API v13 (PostgREST) tightened JWT validation on 2025-07-24 and broke some custom JWT setups. Re-importing the custom signing key per the updated docs resolves the issue.
Dashboard updates for 18 Aug to 1 Sep 2025: expiration dates for Personal Access Tokens, synced report tooltips, refreshed Auth Policies and Integrations pages, and Assistant refinements.
Personal Access Tokens now support expiration dates (preset, custom up to one year, or never) and usage tracking updated every 15 minutes to help identify unused tokens.
Supabase Storage splits egress into cached and origin tiers with separate quotas. Cached egress is now $0.03 per GB, three times cheaper than origin egress, on Free and paid plans.
Supabase Auth gains OAuth 2.1 authorization server capabilities (Public Beta), turning your project into an identity provider for third-party apps and MCP clients.
Edge Functions now run Deno 2.1 in every region. No action required; fall back to Deno 1.45 via the forceDenoVersion=1 query parameter if you hit compatibility issues.
realtime-js 2.15.1 and supabase-js 2.55.0 require Node.js < 22 users to install ws and pass it as the realtime.transport option. Node.js 22+ and browsers need no change.
The Python gotrue and supafunc packages are deprecated in favor of supabase_auth and supabase_functions. Update imports; supabase-py 2.18.1 drops the old packages.
Supabase Postgres image 17.4.1.062 was withdrawn after an issue was found. New projects use an earlier release; existing projects on this version should upgrade once a fix ships.
A unified Logs view in the Supabase dashboard is coming soon, combining logs across all services with improved filtering and real-time updates. Sign up for early access.
Supabase JS libraries (supabase-js, auth-js, realtime-js, functions-js, storage-js, postgrest-js) drop Node.js 18 support on 2025-10-31. Upgrade to Node.js 20 or later.
A Realtime Settings screen in the dashboard lets you configure channel restrictions, database connection pool size, and max concurrent clients per project.
Edge Functions now accept a forceFunctionRegion query parameter to pin invocations to a specific region, useful when request headers cannot be controlled (CORS, webhooks).
Edge Functions now offer a Deno 2.1 preview on the hosted platform. Opt in via the forceDenoVersion=2 query parameter or x-deno-version: 2 header to test compatibility.
The upcoming Supabase Postgres 17 bundle drops timescaledb, plv8, plls, plcoffee, and pgjwt. Postgres 15 keeps the extensions until end of life around May 2026; drop them before upgrading.
Supabase Studio brings back tabs in the Table Editor and SQL Editor, letting you switch between tables across schemas or between snippets without navigating the list. Now fully rolled out.
Supabase developer update for April 2025: project-scoped roles on Team plans, the MCP server works with VS Code and deploys Edge Functions, plus Infinite Query and Social Auth in the UI Library.
Supabase Studio dashboard updates from 21 Apr to 5 May 2025: sort columns from the Table Editor column header, set a billing address and billing name when creating or upgrading an organization.
Supabase Studio dashboard updates from 7 to 21 Apr 2025: revamped organization layout (Feature Preview), redesigned billing breakdown, database upgrade logs, and Feature Previews on self-hosted.
Supabase project-scoped roles are now available on Team plans. Restrict an organization member to specific projects with per-project permissions, useful for security boundaries and HIPAA compliance.
Supabase developer update for March 2025 and Launch Week 14: the official Supabase MCP server, the Supabase UI Library on shadcn, Realtime Broadcast from Database, and declarative schemas.
Supabase Studio dashboard updates from 24 Feb to 7 Apr 2025 covering Launch Week 14: create, edit, test, and deploy Edge Functions in the dashboard, plus Table Editor and SQL Editor tabs.
On 2025-04-02 the Supabase Management API GET /projects/{ref}/analytics/endpoints/logs.all defaults to a one-minute window and caps explicit ranges at 24 hours. Update clients querying wider ranges.
On 2025-04-04 the Supabase Data API switches experimental routing for GET requests from round-robin across all replicas to geo-routing that targets the nearest available database, lowering latency.
Supabase Dedicated Pooler is now generally available on Pro and above: a co-located PgBouncer instance with lower latency than the Shared Pooler for serverless workloads. Transaction mode, IPv6 only.
On 2025-04-21 Supabase restricts SQL on the auth, storage, and realtime schemas: no creating or dropping tables or functions, no writes to migration tables. Move custom objects elsewhere.
Supabase Edge Functions now run on Deno 2.1 locally via the Supabase CLI. Set deno_version = 2 in config.toml to try it before the hosted runtime upgrade. Report regressions during the preview.
Supabase developer update for February 2025: deploy Edge Functions from the dashboard, CLI, or Management API; new Model Context Protocol docs; and cheaper third-party Auth quotas.
Supabase third-party Auth quotas now match standard Auth: 50,000 MAU on the Free Plan and 100,000 MAU on Pro and Team. Overage stays at $0.00325 per MAU. Effective immediately, no action required.
Supabase Studio dashboard updates from 10 to 24 Feb 2025: the new Inline Editor (Feature Preview) for running SQL anywhere, plus Auth, Billing, Edge Functions, and Logs improvements.
The Supabase Management API now exposes endpoints to deploy a single Edge Function and to bulk-update functions atomically, useful for integrations and CI flows that do not depend on the Supabase CLI.
Supabase Studio Inline Editor (Feature Preview) opens a SQL editor anywhere in the dashboard, with an inline AI assistant (cmd+k) and a SQL-first flow for creating policies, triggers, and functions.
Supabase CLI 2.13.3 beta adds supabase functions deploy --use-api to deploy Edge Functions without Docker and to import files outside the supabase/ directory, ideal for monorepos and CI.
Supabase Studio dashboard updates from 27 Jan to 10 Feb 2025: deploy Edge Functions via the AI Assistant, Auth settings consolidated, reference rows in popovers, Security Definer view fix.
Supabase is deprecating Fly.io Postgres managed by Supabase on 2025-04-11. Signups are disabled; existing projects are removed on that date. Migrate to Supabase Postgres or Fly native Postgres.
Supabase developer update for January 2025: third-party Auth with Firebase reaches GA, stacked log charts highlight errors, supabase-js gains JSON type inference and stricter filter type validation.
Supabase Studio dashboard updates from 13 to 27 Jan 2025: stacked log charts surface errors and warnings, three new disk autoscale parameters, and a flat SQL Editor search list with snippets surfaced.
The Supabase Free Plan 0.5 GB database size limit now applies per active project rather than per organization. Paused and deleted projects no longer count toward the cap. Effective immediately.
Supabase developer update for December 2024: new Integrations page, AI Assistant fixes for Security and Performance advisors, inline AI in the SQL Editor, and Vercel Branching support.
supabase-js 2.48.0 infers types for JSON fields when querying with the -> selector. Define a custom JSON type with MergeDeep and the SDK returns the correct shape for nested selections.
Supabase CLI 2.7.0 bundles static files with Edge Functions. Declare files in config.toml under static_files and read them at runtime via Deno APIs. Supports Wasm modules and HTML templates.
Supabase organizations can now top up their credit balance from billing settings. Topped-up credits never expire, apply to future invoices only, and are not refundable. Available on all paid plans.
Supabase Studio dashboard updates from 30 Dec 2024 to 13 Jan 2025: Log Explorer detail panel UX overhaul, S3 protocol toggle in Storage settings, credit balance top-up, and assorted bug fixes.
Supavisor deprecates Session Mode on port 6543 on 2025-02-28; after that date port 6543 only supports Transaction Mode. Move Session Mode clients to port 5432. Transaction-only users need no action.
supabase-js 2.47.12 now type-checks values passed to the eq, neq, and in query filters, including enums, across tables, views, and nested relations. LSP autocompletes enum values.
Supabase Edge Functions can now load NPM modules from a custom private registry, configured with NPM_CONFIG_REGISTRY in .env or on the deploy command. Requires Supabase CLI 2.2.8 or newer.
Dashboard updates: mobile navigation lands for the dashboard, inline AI Assistant completions in the SQL Editor via CMD/CTRL+K, and bulk delete for up to 20 Auth users at a time.
Dashboard updates from Launch Week 13: a unified Integrations page, the AI Assistant V2 available across the dashboard, Supabase Cron, Supabase Queues, and Restore to a new project.
The Slack v1 OAuth provider in Supabase Auth is deprecated in favour of the new Slack (OIDC) provider. Migrate before 2025-01-15, when the legacy provider is removed from the dashboard.
On 2024-11-22, Supabase removes app.settings.jwt_secret from the postgres database. SQL functions calling current_setting('app.settings.jwt_secret') must migrate to Vault.
Dashboard updates: Table Editor performance work cuts perceived load times via query optimizations and prefetching, plus Auth user-sort fixes and Storage image-transform toggles.
supabase-js 2.46.2-rc.3 fixes PostgREST type inference: embeddings now correctly infer single vs array results and object embeddings model nullability. May require regenerating database types.
Supabase Edge Functions now support a per-function deno.json or deno.jsonc file for managing imports and dependencies. Requires Supabase CLI v1.215.0 or later.
Supabase Edge Functions now accept a custom entrypoint via config.toml, so you can author functions in .js, .jsx, .tsx, or .mjs instead of TypeScript. Requires Supabase CLI 1.215.0 or later.
Dashboard updates: Auth email templates now run a SpamAssassin-powered spam check, plus sorting users by last sign-in and a Storage fix for the Developer role.
Supabase Edge Functions can now import npm packages from private registries via an .npmrc file under supabase/functions. Requires Supabase CLI v1.207.9 or later.
Dashboard updates: a new organization-level disk size overview for paid plans, plus Table Editor CSV export and SQL Editor fixes for the local dashboard.
September 2024 developer update: the official Supabase + Vercel integration ships, Edge Functions boot 3x faster and are 2x smaller, and Supabase raises an $80M Series C.
Supabase docs now split into Build and Manage top-level menus, with a new Deployment section and a Monitoring and troubleshooting section to make features and guides easier to find.
Dashboard updates: the Auth users page gets a new data-grid view with detail panels, ban controls, provider filters, and a timestamp helper across Logs collections.
The Supabase Data API and Edge Functions no longer return XHTML on shared domains. Projects that need XHTML responses must enable the Custom Domain add-on. Affected projects notified.
On 2024-10-15, Enterprise organizations lose Developer role write access to project API, Auth, Storage, Edge Functions, and Logs configuration. Read-Only role is unchanged.
Dashboard updates: deploy up to five Read Replicas on XL and larger compute sizes, plus a new SQL Editor warning for UPDATE queries missing a WHERE clause.
Supabase Read Replicas now scale to five per project on XL or larger compute add-ons, up from two. Smaller compute sizes keep the existing two-replica limit.
From 2024-09-26, Supabase Auth's default email provider sends only to organization members. Projects relying on default email auth must configure custom SMTP or a Send Email Auth Hook.
August 2024 developer update recaps Launch Week 12: postgres.new in-browser Postgres with an AI interface, Realtime Broadcast and Presence authorization, and Log Drains.
Supabase Auth is adding asymmetric JWT signing keys with a public JWKs endpoint and a new getClaims() method. Projects created after 2025-05-01 default to RSA asymmetric keys.
Dashboard updates: Schema Visualizer node positions now persist in local storage, plus SQL Editor query-size validation and Table Editor fixes for empty tables and large JSON fields.
Supabase Edge Runtime 1.57 is now serving Edge Functions and is compatible with Deno 1.45. Local development picks it up via Supabase CLI 1.192.5 or later. No action required.
Dashboard updates: upgrade an organization directly from the pricing page, payment method UX fixes for expired cards, and pick which schemas to share with the Supabase AI Assistant.
Dashboard updates: SQL Editor now organizes Private, Favourites, and Shared snippets into folders, with a compute size badge and a refreshed AI Assistant model.
Paid plan database billing moves to hourly proration on provisioned disk on 2024-08-26. First 8 GB per project included, then $0.000171 per GB-hour. Free Plan unaffected.
Supabase daily backups switch to physical backups for any project larger than 15 GB, down from the previous threshold. Backups taken this way can no longer be downloaded from the dashboard.
July 2024 developer update previews Launch Week 12 and ships Data API hardening (disable, custom schema), hourly Storage billing, and more Edge Functions included on every plan.
Custom Domain endpoints move from the Let's Encrypt cross-signed chain to the self-signed chain on 2024-09-09. Very old clients such as Android 7.0 and below may lose trust.
Usage data on Supabase invoices and the org usage page now refreshes within one hour instead of 24. Invoices show per-project breakdowns for Compute, Egress, and Realtime Messages.
IPv4, Custom Domain, and Point-in-time Recovery add-ons move to hourly usage-based billing on 2024-08-26. Monthly prices are unchanged. No more upfront charges or prorated credits.
Storage Size billing moves to hourly proration on 2024-08-26. Prices and quotas are unchanged. Short-lived projects and Branching users see lower bills. No action required.
Wrappers 0.4.1 ships the WebAssembly Foreign Data Wrapper in public alpha, with new Snowflake and Paddle Wasm FDWs and a path for community-built wrappers.
June 2024 developer update: Edge Runtime Inspector for CLI debugging, view and abort running queries in Studio SQL Editor, and log drains via the ELK stack integration.
Supabase HTTP APIs no longer use DigiCert as the root CA. Clients that trust only DigiCert must update their trust store to include the Cloudflare CAs Supabase now uses.
Edge Functions usage-based billing is removed. Free Plan includes 25 functions, Pro 500, Team 1000, Enterprise unlimited. No extra charges for paid plans that exceed previous limits.
Dashboard updates: projects can now expose a dedicated api schema instead of public for the Data API, plus SQL Editor and Logs Explorer fixes.
On 2024-07-26, Supabase removes Developer and Read-Only role access to GitHub and Vercel integration management at the organization level. Existing integrations keep working.
Postgres 13 is deprecated on Supabase. Upgrade affected projects to Postgres 15 before 2024-11-15, when remaining Postgres 13 projects will be auto-upgraded or paused.
Dashboard updates: option to disable the Data API at project creation, Realtime Broadcast and Presence authorization via RLS on realtime.messages, and faster Table Editor row counts.
Dashboard weekly roll-up: clearer compute pricing during project creation, a default Table Editor sort to keep updated rows in place, and Query Performance index advisor for PostgREST.
From June 24, 2024, paused Free Plan Supabase projects are restorable for 90 days. Projects paused before that date have until September 22, 2024. Paid plans are unaffected.
May 2024 Developer Updates from Consolidation Month: the new @supabase/ssr package, pgvector v0.7.0 with float16 vectors, Edge Functions memory fixes, and standardized Realtime error codes.
Supabase Edge Functions hosted platform now runs Edge Runtime v1.54, compatible with Deno 1.43. Local development with Supabase CLI v1.176.10 or later picks up the same compatibility.
Dashboard weekly roll-up from Consolidation Month: new alerts for client crashes, Vitest and Playwright test infrastructure, and Table and SQL Editor safeguards for large workloads.
The @supabase/ssr package moves to its own repo and a v0.4 reimplementation in mid-June 2024, with a new getAll/setAll cookie API. The current API will be deprecated at v1.0.0.
Supabase Log Drains enter Private Alpha for Team and Enterprise customers, starting with Datadog. Elastic/Filebeat and Syslog are in the works. Sign up via the interest form.
The supabase-grafana Fly deployment instructions now add a persistent volume and disable auto-stop. Fly deployments from December 10, 2023 to May 16, 2024 should reapply the config.
Dashboard weekly roll-up: the conversational AI assistant in the SQL Editor is now on by default, and Postgres errors in the Table Editor surface more contextual hints.
April 2024 Developer Updates: Supabase reaches General Availability, plus Edge Functions AI model support, Auth anonymous sign-ins, Storage S3 protocol, and Security and Performance Advisors.
Supabase Edge Functions now support JSR packages via jsr: imports, including modules like Oak. Local development requires Supabase CLI v1.166.1 or later.
Dashboard weekly roll-up: Table Editor foreign key fixes, SQL Editor column sizing, a Create policy CTA in Authentication, Storage upload size validation, and Query Performance search fixes.
Dashboard weekly roll-up from GA Week: Auth anonymous sign-ins, Storage S3 protocol support, new Security, Performance, and Index Advisors, and four new foreign data wrappers.
March 2024 Platform Updates: higher Supavisor client connection limits, a conversational AI assistant in the SQL Editor, port 6543 transaction-mode only, and v2 platform architecture migration.
Supavisor client connection limits double or more on Small (400), Medium (600), Large (800), and XL (1,000) compute instances. Pricing is unchanged and the limits apply automatically.
Realtime Authorization for Broadcast and Presence is now in Public Beta, gating channel access via Postgres RLS policies on the realtime.messages table.
Dashboard weekly roll-up: a hybrid RLS policy editor that shows the underlying SQL, and Supavisor pooler port 6543 set to transaction mode only with session mode on 5432.
Supabase Platform v2 architecture rolls out to Free Plan projects from March 20, 2024, unbundling Storage, Realtime, and the pooler. Existing projects migrate gradually with email notice.
Dashboard weekly roll-up: a conversational AI assistant lands in the SQL Editor as a feature preview, plus fixes to table creation, snippet names, and the new RLS UI.
February 2024 Platform Updates: Matryoshka embeddings for vector search, framework Connect snippets in Studio, PostgREST 12 aggregate functions, and an official Supabase Terraform provider.
Dashboard weekly roll-up: templates and richer prompts in the RLS assistant, collapsible navigation, SQL Editor charts, and foreign key management restored to the column side panel.
Dashboard weekly roll-up: launch paid projects on bigger compute immediately, a more prominent Table Editor search, resizable Table and SQL Editor sidebars, and Expo React Native connect guides.
Paid Supabase organizations can now pick a larger compute size when creating a project, skipping the previous Micro-then-upgrade flow. Up- and downgrades remain available.
Dashboard weekly roll-up: Connect button on project home with framework and ORM snippets, refreshed Table Editor sidebar and header, and an Auth user details view.
Dashboard weekly roll-up: bulk delete in the SQL Editor, query performance search and sort, a refreshed Logs Explorer, and Table Editor support for composite foreign keys.
January 2024 Platform Updates: Supavisor replaces PgBouncer for pooling, direct connections move to IPv6 with an IPv4 add-on available, plus Studio table-editor and email-template enhancements.
Dashboard weekly roll-up: clearer organization billing breakdown, SQL Editor snippet previews, larger Table Editor text cell editing with Markdown preview, and Auth email template preview.
Dashboard weekly roll-up: simplified Database connection UI, IPv6 support and normalization for Network Restrictions, the new IPv4 add-on toggle, and removal of the legacy LinkedIn provider.
Paid Supabase projects can now enable an IPv4 add-on for direct database connections at $4 per month. Projects using Supavisor or supporting IPv6 do not need it.
From January 24, 2024, Supavisor enforces project Network Restrictions. Existing restrictions propagate automatically; projects without restrictions are unaffected.
Dashboard weekly roll-up: column-level privileges management in the dashboard, Table Editor cell copy shortcuts, role-impersonation safeguards, and a Storage Explorer empty-bucket action.
Launch Week X recap: Studio AI Assistant and user impersonation, Edge Functions Node and npm support, Supabase Branching, Auth Identity Linking and Hooks, and Read Replicas.
Supavisor 1.1.6 fixes a bug that caused prepared statements to fail when using session mode. No action required.
Supavisor 1.1.5 starts pools with 10 connections and grows up to the tenant pool size, preventing over-allocation of Postgres max_connections during PgBouncer migrations.
Dashboard weekly roll-up: smoother Auth users pagination, fixes for RLS schema selection and uppercase enum deletion, and alphabetical sorting for RLS policies.
Supavisor v1.1.2 adds an allow_list field on tenants for CIDR-based network restrictions and a configurable client_heartbeat_interval to detect dead client connections.
Supabase Platform lowers the daily physical-backup threshold to 40 GB. Restores work as before, but backups taken this way are no longer downloadable from the dashboard.
Supabase Studio Launch Week X follow-up: AI-assisted RLS editor, Postgres role and user impersonation across editors, the Realtime Inspector, and a new Feature Previews surface.
Supabase April 2021 update: Dashboard Light Mode ships, the main repo is internationalized into 20+ languages, and the open-source Stripe Sync Engine is released for experimentation.
Supabase August 2021 update: closed a $30M Series A, opened the WALRUS RLS-for-Realtime RFC, launched the Seoul region, and added custom SMS templates to Auth.
Supabase July 2021 update: Launch Week II ships Auth v2 with phone OTP, Storage Beta with public buckets and streaming, Dashboard v2, and Postgres 13 for new projects.
Supabase June 2021 update: Vercel integration, Discord OAuth login, public Storage buckets and upserts, a Table Policy editor, and new guides for Postgres Full-Text Search and OAuth.
Supabase May 2021 update: Apple and Twitter OAuth providers ship, the Tokyo region opens, a new Storage policy editor lands, and community Go and Swift libraries kick off.
Supabase October 2021 update: Slack, Spotify, and MessageBird Auth providers, multi-schema support in the Dashboard and API, plus new Database Functions and Auth guides.
Supabase February 2023 update: GraphiQL editor in the Dashboard, pgvector-powered docs search, Edge Functions CLI multi-serve, and a 1.3GB-to-250MB Postgres Docker image rebuild.
Supabase January 2023 update: pgvector ships for storing OpenAI embeddings, Supabase Clippy launches docs search, and pg_graphql adds Views, Materialized Views, and Foreign Tables.
Supabase September 2022 update: three Kaizen weeks close 250+ issues, Auth UI launches on Product Hunt, and an open-source Postgres WASM ships with Snaplet.
Supabase September 2023 update: Realtime broadcast via REST, Supavisor pooling on all new projects, the Airtable Foreign Data Wrapper, and HNSW support in the Vecs Python client.
Supabase November 2021 platform update: PostgREST 9.0, Realtime 0.19.0, Storage 0.10.0, GoTrue 2.2.10, and Postgres 14.1 for new projects. Custom auth functions need updating for PG14.
Supabase April 2023 Launch Week 7: open-source Supabase Logs, self-hosted Edge Runtime, Storage v3 with resumable 50GB uploads, SSO in Auth, Studio 2.0, and dbdev for Postgres packages.
Supabase August 2023 Launch Week 8: pgvector 0.5.0 with HNSW, Hugging Face support, Studio 3.0, the Integrations Marketplace, Supavisor 1M-connection pooling, plus SOC 2 and HIPAA.
Supabase June 2023 update: native Sign in with Apple and Google in Auth, Kakao OAuth, a revamped billing experience in Studio, and a wave of CLI features for migrations and functions.
Supabase May 2023 update: Supabase Vector toolkit launches, the Vault encrypted-secrets extension reaches all projects, and Next.js Auth Helpers add full App Router support with PKCE.
Supabase November 2022 update: Remix Auth Helpers ship with supabase-js v2 and TypeScript support, plus a new Edgy Edge Functions video series and three new function examples.
Supabase October 2022 update: supabase-js v2 and supabase-flutter v1 ship, the Next.js quickstart adopts Next.js 13, pgTAP database testing lands, and Edge Functions add GET/PUT/PATCH/DELETE.
Supabase October 2023 update: @supabase/ssr launches for Next.js 14 server-side auth, pgvector outperforms Pinecone in benchmarks, and MFA arrives for Supabase Studio accounts.
Supabase September 2021 update: AbortController support in supabase-js for long-running queries, improved Table Editor column types and unique constraints, and revamped Auth docs.
Supavisor 1.0 ships with named prepared statements, read-replica query load balancing, a client_idle_timeout option, and a PgBouncer migration guide. Hosted rollout starts next week.
Supabase Studio weekly roundup: Table Editor side-panel renders the correct row values for Listbox columns, and branching now prompts you to turn on point-in-time recovery.
Supabase Studio ships a revamped organization usage page with per-project breakdowns, daily compute stats, custom timeframes, overage costs, and limit warnings.
Supabase Database no longer allows direct inserts or updates on the pg_cron cron.job table. Schedule and modify jobs via the pg_cron functions documented in the guides.
Supabase Studio weekly roundup: backups page accessible during restores, MFA status in organization members, SQL Editor migration/seed downloads, and Table Editor fixes.
Supabase Auth deprecates the LinkedIn OAuth provider in favor of LinkedIn (OIDC). Projects using a pre-1 Aug 2023 LinkedIn app must migrate credentials by 4 Jan 2024.
Supabase Edge Functions secrets (SUPABASE_DB_URL, SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY) now update automatically when you reset the database password or JWT secret.
Supabase Studio no longer offers Transparent Column Encryption in the Table Editor UI. Existing TCE columns keep working; new encryption must be managed via SQL and pgsodium.
Direct Postgres connections from Supabase Edge Functions are now secured with SSL automatically. No client configuration changes are required.
Supabase Realtime handles failures of its internal realtime schema migrations more gracefully, improving reliability when projects connect. No action required.
Databases over 100GB now use physical daily backups. Restores work as before, but these backups can no longer be downloaded from the dashboard.
Postgres 12 is deprecated. Self-serve upgrade to Postgres 15 opens 27 October 2023; all remaining Postgres 12 databases auto-upgrade on 2023-11-27.
PgBouncer and direct IPv4 database connections are deprecated. Projects must migrate to Supavisor or the IPv4 add-on by 2024-01-26; db.projectref.supabase.co resolves to IPv6.
Supabase billing moves from project-based to organization-based, adding project transfers, consolidated invoices, a self-serve Team plan, and 1GB extra Free egress.
Supabase is removing superuser access from the dashboard SQL Editor. Affected projects must run a one-time migration during the opt-in period (5 Oct to 5 Nov 2022).