Supabase

The Supabase Management API `logs.all` analytics endpoint is being removed on 2026-09-23. Scripts must migrate to the new ClickHouse-backed `logs` endpoint, which only accepts ClickHouse SQL.

The Supabase Management API `logs.all` analytics endpoint is being removed on 2026-09-23. Scripts must migrate to the new ClickHouse-backed `logs` endpoint, which only accepts ClickHouse SQL.

Multiple breaking changes detected in this Supabase changelog dump, including the removal of the Management API `logs.all` endpoint on 2026-09-23, deprecation of extension version pinning, Envoy replacing Kong as the default API gateway for self-hosted, Realtime schema lockdown, OAuth token endpoint returning HTTP 200 instead of 201, tables no longer auto-exposed to Data/GraphQL API, and several others. The most immediately impactful is the `logs.all` endpoint removal with a hard cutover date.

The Supabase Management API `logs.all` analytics endpoint is being removed on 2026-09-23 and must be replaced with the new ClickHouse-backed `logs` endpoint, which only accepts ClickHouse SQL. Multiple other breaking changes are also present in this changelog, including removal of the `realtime` schema modification rights, deprecation of extension version pinning, and self-hosted gateway changes.

Multiple breaking changes detected in this Supabase changelog diff, most critically the removal of the Management API `logs.all` analytics endpoint on 2026-09-23, which requires migration to the new ClickHouse-backed logs endpoint using ClickHouse SQL. Additional high-severity breaking changes include: Envoy replacing Kong as default API gateway for self-hosted (week of 2026-08-09), the `realtime` schema being fully locked down, `API_EXTERNAL_URL` path change for self-hosted auth, tables no longer auto-exposed to Data/GraphQL API, and the OAuth token endpoint returning HTTP 200 instead of 201.

This diff contains multiple breaking changes across the Supabase platform, with the most critical being the removal of the Management API `logs.all` analytics endpoint on 2026-09-23, the deprecation of extension version pinning (ignored from 2026-08-05), the Envoy replacing Kong as default API gateway for self-hosted deployments (week of 2026-08-09), and Realtime schema being fully locked down. Additional breaking changes include OAuth token endpoint returning HTTP 200 instead of 201, tables no longer auto-exposed to Data/GraphQL APIs, pg_graphql disabled by default, and removal of OpenAPI spec access via anon key.

The Supabase Management API `logs.all` analytics endpoint is being removed on 2026-09-23 and must be migrated to the new ClickHouse-backed `logs` endpoint, which only accepts ClickHouse SQL. Additionally, multiple other breaking changes are present in this diff including self-hosted gateway changes, realtime schema lockdown, OAuth token endpoint status code change, and more.

Multiple breaking changes are present in this diff, most critically the removal of the Management API `logs.all` analytics endpoint on 2026-09-23, and the deprecation/removal of several other endpoints and behaviors. The most immediately actionable critical change is the `logs.all` endpoint removal, but there are numerous other breaking changes across auth, database, self-hosted, and realtime surfaces.

Multiple breaking changes are present in this diff, including the removal of the Management API `logs.all` analytics endpoint on 2026-09-23, deprecation of extension version pinning, Envoy replacing Kong as the default API gateway for self-hosted, Realtime schema lockdown, OAuth token endpoint returning HTTP 200 instead of 201, tables no longer auto-exposed to Data/GraphQL APIs, and several others. The most immediately actionable is the `logs.all` endpoint removal with a hard cutoff date.

The Supabase Management API `logs.all` analytics endpoint is being removed on 2026-09-23, requiring migration to the new ClickHouse-backed `logs` endpoint which only accepts ClickHouse SQL. Additionally, multiple other breaking changes are present in this diff including Envoy replacing Kong as default API gateway, realtime schema lockdown, OAuth token endpoint returning HTTP 200 instead of 201, and several self-hosted configuration changes.

The Supabase Management API `logs.all` analytics endpoint will be removed on 2026-09-23. Scripts must migrate to the new ClickHouse-backed `logs` endpoint, which accepts ClickHouse SQL only.

Multiple breaking changes detected across Supabase APIs and services, with the most immediately actionable being the removal of the Management API `logs.all` analytics endpoint on 2026-09-23 (must migrate to the new ClickHouse-backed logs endpoint), the deprecation/ignoring of extension version pinning from 2026-08-05, and the self-hosted Envoy gateway replacing Kong from 2026-08-09. Additional breaking changes include the OAuth token endpoint switching from HTTP 201 to 200, tables no longer auto-exposed to Data/GraphQL APIs, and restrictions on auth/storage/realtime schemas.

Multiple breaking changes are present in this diff, most critically the removal of the Management API `logs.all` analytics endpoint on 2026-09-23, which requires migration to the new ClickHouse-backed logs endpoint using ClickHouse SQL only. Additional high-severity breaking changes include: Envoy replacing Kong as default API gateway for self-hosted (2026-08-09), realtime schema locked down against modifications (2026-07-14), OAuth token endpoint changing from HTTP 201 to 200 (2026-06-01), tables no longer auto-exposed to Data/GraphQL API (2026-10-30 enforcement), and several self-hosted infrastructure breaking changes.

The Supabase Management API `logs.all` analytics endpoint is being removed on 2026-09-23 and must be replaced with the new ClickHouse-backed `logs` endpoint, which only accepts ClickHouse SQL. Multiple other breaking changes are also present including Envoy replacing Kong as default API gateway, realtime schema lockdown, OAuth token endpoint returning HTTP 200 instead of 201, and several self-hosted configuration changes.

The Supabase Management API `logs.all` analytics endpoint is being removed on 2026-09-23 and must be replaced with the new ClickHouse-backed `logs` endpoint, which only accepts ClickHouse SQL. Additionally, multiple other breaking changes are included in this diff spanning API endpoints, self-hosted gateway changes, schema lockdowns, and more.

The Supabase Management API `logs.all` analytics endpoint is being removed on September 23, 2026, replaced by a new ClickHouse-backed `logs` endpoint with a unified table, different SQL dialect requirements, and a flat `log_attributes` map instead of nested metadata arrays.

The Supabase Management API `logs.all` analytics endpoint is being removed on September 23, 2026, replaced by a new ClickHouse-backed `logs` endpoint that uses a different SQL dialect, a unified table structure, and a flat `log_attributes` map instead of nested metadata arrays.

The Supabase Management API `logs.all` analytics endpoint is being removed on September 23, 2026. Log querying must migrate to the new ClickHouse-backed `logs` endpoint, which uses a different SQL dialect, a unified table structure, and a flat `log_attributes` map instead of nested metadata arrays.

The Supabase Management API `logs.all` analytics endpoint is being removed on September 23, 2026. Log querying must migrate to the new ClickHouse-backed `logs` endpoint, which uses a different SQL dialect, a unified table structure, and a flat `log_attributes` map instead of nested metadata arrays.

The Supabase Management API `logs.all` analytics endpoint is being removed on September 23, 2026. Log querying is migrating to a new ClickHouse-backed `logs` endpoint that uses a unified table, ClickHouse SQL dialect, and flat `log_attributes` map instead of nested metadata arrays.

The Supabase Management API `logs.all` analytics endpoint is being removed on September 23, 2026, replaced by a new ClickHouse-backed `logs` endpoint that requires ClickHouse SQL, uses a unified table with `source_name` filtering, and changes nested field access from `metadata` arrays to a flat `log_attributes` map.

The Supabase Management API `logs.all` analytics endpoint (`/analytics/endpoints/logs.all`) is being removed on September 23, 2026. Log querying is migrating to a new ClickHouse-backed `logs` endpoint with a different SQL dialect, unified table structure, and flattened field access model.

The Supabase Management API `logs.all` analytics endpoint is being removed on September 23, 2026, replaced by a new ClickHouse-backed `logs` endpoint that requires ClickHouse SQL, uses a unified table with `source_name` filtering, and flattens nested metadata into `log_attributes`. Additionally, Postgres extension version pinning is deprecated starting August 5, 2026, where explicit VERSION clauses will be silently ignored (and later rejected).

The Supabase Management API `logs.all` analytics endpoint is being removed on September 23, 2026, and replaced with a new ClickHouse-backed `logs` endpoint that uses a different SQL dialect, unified table structure, and flat `log_attributes` map instead of nested metadata arrays.