Supabase APIBreaking changehigh
Supabase removes the logs.all analytics endpoint on Sep 23, 2026
- Detected
- Aug 3, 2026
- Effective
- Sep 23, 2026(took effect 54 days ago)
- Confidence
- 97%
What changed
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).
What to do
For logs.all: update endpoint path from analytics/endpoints/logs.all to analytics/endpoints/logs, rewrite SQL to ClickHouse dialect, replace per-source table queries with WHERE source_name = '...' on the unified logs table, and replace CROSS JOIN unnest(metadata) patterns with log_attributes['field.path'] map access. For extension pinning: remove VERSION '...' and UPDATE TO '...' clauses from all migration scripts and tooling.
Affected
endpoint: GET /analytics/endpoints/logs.allendpoint: GET /analytics/endpoints/logsparam: VERSION clause in CREATE/ALTER EXTENSIONparam: source_name (logs unified table filter)model: log_attributes (replaces metadata unnest pattern)Source: 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