BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Breakwatch//API change radar//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:Supabase API deadlines (Breakwatch)
X-WR-CALDESC:Supabase API breaking changes and deprecation dates: https://w
 ww.breakwatch.ai/radar/supabase
REFRESH-INTERVAL;VALUE=DURATION:PT12H
X-PUBLISHED-TTL:PT12H
BEGIN:VEVENT
UID:supabase-1787551204978-86e319e5@breakwatch.ai
DTSTAMP:20260824T060004Z
DTSTART;VALUE=DATE:20260923
DTEND;VALUE=DATE:20260924
SUMMARY:Supabase removes the logs.all Management API endpoint on Sep 23\, 2
 026
DESCRIPTION:The Supabase Management API logs.all analytics endpoint is bein
 g removed on 2026-09-23 and must be replaced with the new ClickHouse-backe
 d logs endpoint\, which only accepts ClickHouse SQL. Multiple other breaki
 ng changes are also present including Envoy replacing Kong as default API 
 gateway\, realtime schema lockdown\, OAuth token endpoint returning HTTP 2
 00 instead of 201\, and several self-hosted configuration changes.\n\nWhat
  to do: Migrate scripts from logs.all to the new logs endpoint using Click
 House SQL before 2026-09-23. Additionally: update OAuth token checks from 
 status 201 to any 2XX\; if self-hosted\, prepare for Envoy replacing Kong 
 (week of 2026-08-09) and opt back into Kong if needed\; note that extensio
 n version pinning in CREATE/ALTER EXTENSION is ignored from 2026-08-05\; a
 nd review all other breaking changes for their respective effective dates.
 \n\nDetails: https://www.breakwatch.ai/radar/supabase/changes/supabase-rem
 oves-logs-all-management-api-endpoint-sep-1787551204978-86e319e5
URL:https://www.breakwatch.ai/radar/supabase/changes/supabase-removes-logs-
 all-management-api-endpoint-sep-1787551204978-86e319e5
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Supabase removes the logs.all Management API endpoin
 t on Sep 23\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:supabase-1790575204689-c63b0be3@breakwatch.ai
DTSTAMP:20260928T060004Z
DTSTART;VALUE=DATE:20260928
DTEND;VALUE=DATE:20260929
SUMMARY:Supabase ships breaking Postgres 15.19/17.11 updates on Sep 28\, 20
 26
DESCRIPTION:Supabase is rolling out PostgreSQL 15.19/17.11 minor releases t
 hat include four potentially breaking changes: ltree indexes may need rein
 dexing\, pgcrypto stops decrypting legacy-cipher (Blowfish/CAST5) PGP data
  by default\, btree_gist indexes on float columns containing NaN need rein
 dexing\, and custom operators with non-built-in selectivity estimators now
  require superuser to recreate.\n\nWhat to do: Run the provided detection 
 queries for each affected area. Reindex affected ltree and btree_gist inde
 xes using REINDEX INDEX CONCURRENTLY. Re-encrypt pgcrypto data using ciphe
 r-algo=aes256. Recreate custom operators without RESTRICT/JOIN clauses or 
 switch to built-in estimators. Upgrade available in dashboard from 2026-09
 -28.\n\nDetails: https://www.breakwatch.ai/radar/supabase/changes/supabase
 -ships-breaking-postgres-15-19-17-11-1790575204689-c63b0be3
URL:https://www.breakwatch.ai/radar/supabase/changes/supabase-ships-breakin
 g-postgres-15-19-17-11-1790575204689-c63b0be3
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Supabase ships breaking Postgres 15.19/17.11 updates
  on Sep 28\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:supabase-1793815205009-6bee6b34@breakwatch.ai
DTSTAMP:20261104T180005Z
DTSTART;VALUE=DATE:20261102
DTEND;VALUE=DATE:20261103
SUMMARY:Supabase CLI v3 defaults to local\, requires --remote on Nov 2\, 20
 26
DESCRIPTION:Supabase CLI v3.0.0 changes default command targets (local inst
 ead of hosted)\, requires explicit --remote and --yes flags for hosted/una
 ttended operations\, removes deprecated commands and config keys\, and is 
 now installed by default via npm\, Homebrew\, Scoop\, and setup-cli. Pipel
 ines and CI scripts that install the latest CLI without pinning a version 
 are immediately affected.\n\nWhat to do: Add --remote to any command targe
 ting a hosted project\, add --yes to unattended hosted changes in CI\, ren
 ame [inbucket] to [local_smtp] in config.toml\, and pin v2 (npm install su
 pabase@v2.stable) if not ready to migrate.\n\nDetails: https://www.breakwa
 tch.ai/radar/supabase/changes/supabase-cli-v3-defaults-local-requires-remo
 te-nov-1793815205009-6bee6b34
URL:https://www.breakwatch.ai/radar/supabase/changes/supabase-cli-v3-defaul
 ts-local-requires-remote-nov-1793815205009-6bee6b34
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Supabase CLI v3 defaults to local\, requires --remot
 e on Nov 2\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:supabase-1791979203670-e9e842e9@breakwatch.ai
DTSTAMP:20261014T120003Z
DTSTART;VALUE=DATE:20261110
DTEND;VALUE=DATE:20261111
SUMMARY:Supabase drops CBC TLS 1.2 cipher suites from its APIs on Nov 10\, 
 2026
DESCRIPTION:Supabase will remove four CBC-mode TLS 1.2 cipher suites (TLS_E
 CDHE_*_WITH_AES_*_CBC_SHA*) from all project HTTP APIs (Auth\, Data API\, 
 Storage\, Realtime\, Edge Functions) starting November 10\, 2026. Clients 
 using only these deprecated ciphers will lose connectivity.\n\nWhat to do:
  Verify that all clients connecting to Supabase over HTTPS support at leas
 t one GCM or ChaCha20-Poly1305 TLS 1.2 cipher or TLS 1.3. Update end-of-li
 fe OS or TLS libraries accordingly before November 10\, 2026.\n\nDetails: 
 https://www.breakwatch.ai/radar/supabase/changes/supabase-drops-cbc-tls-1-
 2-cipher-suites-1791979203670-e9e842e9
URL:https://www.breakwatch.ai/radar/supabase/changes/supabase-drops-cbc-tls
 -1-2-cipher-suites-1791979203670-e9e842e9
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Supabase drops CBC TLS 1.2 cipher suites from its AP
 Is on Nov 10\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:supabase-1794031205237-032a5be1@breakwatch.ai
DTSTAMP:20261107T060005Z
DTSTART;VALUE=DATE:20261111
DTEND;VALUE=DATE:20261112
SUMMARY:supabase-flutter v3 breaks Dart/Flutter API surface with stable rel
 ease on Nov 11\, 2026
DESCRIPTION:supabase-flutter v3 introduces sweeping breaking changes to the
  Flutter/Dart client library\, including renamed packages\, changed API si
 gnatures\, new type system\, and altered defaults (e.g. order() sort direc
 tion). Stable release is planned for November 11\, 2026\, with v2 receivin
 g security fixes for 6 months afterward.\n\nWhat to do: Before upgrading: 
 add ascending: false to all order() calls relying on descending order whil
 e still on v2. Then bump to ^3.0.0\, replace renamed packages (gotrue→su
 pabase_auth\, realtime_client→supabase_realtime\, etc.)\, fix compile er
 rors per the migration guide\, and coordinate simultaneous release of apps
  sharing realtime broadcast channels.\n\nDetails: https://www.breakwatch.a
 i/radar/supabase/changes/supabase-flutter-v3-breaks-dart-flutter-api-surfa
 ce-1794031205237-032a5be1
URL:https://www.breakwatch.ai/radar/supabase/changes/supabase-flutter-v3-br
 eaks-dart-flutter-api-surface-1794031205237-032a5be1
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: supabase-flutter v3 breaks Dart/Flutter API surface 
 with stable release on Nov 11\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:supabase-1791309605920-4948352b@breakwatch.ai
DTSTAMP:20261006T180005Z
DTSTART;VALUE=DATE:20261201
DTEND;VALUE=DATE:20261202
SUMMARY:Supabase removes @supabase/server framework adapters on Dec 1\, 202
 6
DESCRIPTION:The four framework adapters in @supabase/server (/adapters/hono
 \, /adapters/h3\, /adapters/elysia\, /adapters/nestjs) are deprecated and 
 will be removed on December 1\, 2026. Developers must migrate to a framewo
 rk-specific bridge file that wraps @supabase/middleware entries.\n\nWhat t
 o do: Copy the appropriate bridge file for your framework (Hono\, H3\, Ely
 sia\, NestJS\, or TanStack Start) from the Supabase frameworks guide into 
 your project. Add @supabase/middleware as a direct dependency\, replace ad
 apter registrations with bridge calls (e.g.\, toHono([withRequiredClaims()
 \, withSupabaseClient()]))\, and update call sites from nested supabaseCon
 text to flat keys like c.var.supabase and c.var.jwtClaims.\n\nDetails: htt
 ps://www.breakwatch.ai/radar/supabase/changes/supabase-removes-supabase-se
 rver-framework-adapters-dec-1-1791309605920-4948352b
URL:https://www.breakwatch.ai/radar/supabase/changes/supabase-removes-supab
 ase-server-framework-adapters-dec-1-1791309605920-4948352b
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Supabase removes @supabase/server framework adapters
  on Dec 1\, 2026
END:VALARM
END:VEVENT
END:VCALENDAR
