Supabase changed its API changelog

===================================================================
--- before
+++ after
@@ -7,127 +7,82 @@
 RSS
 
 Copy as Markdown
 
-FIXED STALE DATABASE CREDENTIALS LEFT BEHIND AFTER A RESTORE
+READ REPLICAS MOVED TO PROJECT SETTINGS → INFRASTRUCTURE
 
-Jul 30, 2026
+Aug 21, 2026
 
-Bug Fix
+Improvement
 
-A WAL-G physical restore restores the whole PGDATA directory, including pg_authid, so credentials from the backup snapshot overwrote any password rotated after that backup was taken. Credential reapplication was previously only queued when a restore was part of an in-progress clone, so a plain restore to the same project, or an unpause (which shares the same completion path), skipped it entirely and could leave db_user with a stale password. Logical restores are unaffected: pg_dumpall runs with --no-role-passwords, so a logical backup never carries password hashes to begin with.
+Read replica management now lives on Project Settings → Infrastructure, next to compute and disk. Database → Replication is for Pipelines destinations only.
 
-Supabase now reapplies current credentials after every physical restore completes, regardless of whether it is part of a clone.
+What stays the same:
 
-A related fix also closes a data-loss path in cloning status tracking: reapplying credentials for a non-clone restore could, on retry exhaustion, flip an unrelated and already-completed clone's status back to failed, which could let a later stray clone request overwrite that project's data. Status transitions are now scoped to clones that are actually in progress.
+ * Creating, dropping, and managing replicas
+ * The Management API
+ * Read replica docs (updated for the new location)
 
-Database
-Platform
+What changes in the Dashboard:
 
-FIXED A PANIC IN PROJECT METRICS COLLECTION THAT COULD DROP METRICS
+ * Open Project Settings → Infrastructure to list replicas, open the topology, and add a replica
+ * Old replica detail URLs redirect to Infrastructure
+ * Bookmarks that used ?destinationType=Read+Replica on Replication open the Infrastructure add-replica flow
+ * Replication shows a short note pointing to Infrastructure for anyone who still opens that page looking for replicas
 
-Jul 29, 2026
+See the getting started guide for the updated create path.
 
-Bug Fix
+Studio
 
-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.
+FIXED DAILY BACKUPS OCCASIONALLY SKIPPED DUE TO A SCHEDULING TIMEOUT
 
-Each request now gets its own parser instance, so concurrent metrics requests no longer interfere with each other.
+Aug 12, 2026
 
-Observability
-Platform
+Bug Fix
 
-MIGRATION OF SUPABASE MANAGEMENT API LOGS.ALL ANALYTICS ENDPOINT TO LOGS ENDPOINT
+The job that schedules daily backups checks which projects are due on a strict time budget. Under database replica lag, that check could exceed its budget, and with no retry in place the whole 10-minute scheduling window was silently dropped fleet-wide — any project due in that window missed its backup for the day.
 
-Jul 23, 2026
+Backup scheduling now retries on failure, anchored to its original scheduled window so a retry can't skip or re-scan the wrong projects, reads eligibility from the primary database instead of a replica to avoid the lag that triggered the timeout, and no longer lets a project in an unroutable region crash the whole scheduling run. A companion fix (supabase/platform#36499) addresses the underlying slow query.
 
-Breaking Change
+Database
+Platform
 
-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.
+FIXED STALE DATABASE CREDENTIALS LEFT BEHIND AFTER A RESTORE
 
-HOW DO I KNOW IF THIS IMPACTS ME?#
+Jul 30, 2026
 
-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.
+Bug Fix
 
-If you do not call this endpoint, no action is needed. Using logs through the dashboard Logs Explorer is not affected.
+A WAL-G physical restore restores the whole PGDATA directory, including pg_authid, so credentials from the backup snapshot overwrote any password rotated after that backup was taken. Credential reapplication was previously only queued when a restore was part of an in-progress clone, so a plain restore to the same project, or an unpause (which shares the same completion path), skipped it entirely and could leave db_user with a stale password. Logical restores are unaffected: pg_dumpall runs with --no-role-passwords, so a logical backup never carries password hashes to begin with.
 
-WHAT SHOULD I DO?#
+Supabase now reapplies current credentials after every physical restore completes, regardless of whether it is part of a clone.
 
- 1. Update the endpoint path from analytics/endpoints/logs.all to analytics/endpoints/logs.
- 2. Convert your SQL to the ClickHouse dialect. The endpoint only accepts ClickHouse SQL.
- 3. Filter by 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.
+A related fix also closes a data-loss path in cloning status tracking: reapplying credentials for a non-clone restore could, on retry exhaustion, flip an unrelated and already-completed clone's status back to failed, which could let a later stray clone request overwrite that project's data. Status transitions are now scoped to clones that are actually in progress.
 
-Before (query a source table directly):
+Database
+Platform
+2026
 
-_10
-SELECT timestamp, event_message
-_10
-FROM edge_logs
-_10
-ORDER BY timestamp DESC
-_10
-LIMIT 100
+2026
+Bug Fix
 
-After (filter the unified stream by source_name):
+FIXED A PANIC IN PROJECT METRICS COLLECTION THAT COULD DROP METRICS
 
-_10
-SELECT timestamp, event_message
-_10
-FROM logs
-_10
-WHERE source_name = 'edge_logs'
-_10
-ORDER BY timestamp DESC
-_10
-LIMIT 100
+A metrics endpoint could panic under concurrent requests, intermittently stopping metrics from being collected and pushed for a project.
 
-Any query that previously targeted a specific table must now add a source_name filter in its WHERE clause.
+Jul 29
+Bug Fix
+Observability
+Platform
+Breaking Change
 
-ACCESSING NESTED FIELDS#
+MIGRATION OF SUPABASE MANAGEMENT API LOGS.ALL ANALYTICS ENDPOINT TO LOGS ENDPOINT
 
-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.
+The Supabase Management API logs.all endpoint is removed on 2026-09-23. Scripts calling it must migrate to the new ClickHouse-backed logs endpoint, which accepts ClickHouse SQL only.
 
-Before (unnest each level of metadata):
-
-_10
-SELECT timestamp, request.method, header.x_real_ip
-_10
-FROM edge_logs
-_10
-CROSS JOIN unnest(metadata) AS m
-_10
-CROSS JOIN unnest(m.request) AS request
-_10
-CROSS JOIN unnest(request.headers) AS header
-
-After (read from the log_attributes map):
-
-_10
-SELECT
-_10
-timestamp,
-_10
-log_attributes['request.method'] AS method,
-_10
-log_attributes['request.headers.x_real_ip'] AS x_real_ip
-_10
-FROM logs
-_10
-WHERE source_name = 'edge_logs'
-
-TIMELINE#
-
-DateChange23 July 2026Changelog published23 September 2026logs.all endpoint removed for all projects
-
-LEARN MORE#
-
- * Management API reference: the logs endpoint and its parameters
- * Logs & querying documentation: available sources and ClickHouse SQL query examples
-
+Jul 23
+Breaking Change
 Platform
-2026
-
-2026
 Breaking Change
 
 EXTENSION VERSION PINNING IS DEPRECATED IN FAVOR OF DEFAULT VERSIONS