$ cat supabase/week/2026-10-05.log
the week in review · Oct 5 – Oct 11, 2026
CLI 2.120.0 adds persisted logs and OTel traces
By RepoJournal · composed from the cited sources · human-reviewed weekly · methodology
The same period brought loopback bind addresses for native stacks, Realtime presence metrics, and four ClickHouse and Snowflake replication fixes.
v2.120.0 supabase/cli
Service logs now persist to disk and ship to Analytics, and CLI runs can export OpenTelemetry traces, so a failing local stack leaves evidence behind instead of scrollback. Stack commands also picked up usability changes alongside the bug fixes.
feat(native): accept a loopback bind address for realtime, pooler, and analytics supabase/slim-services
Realtime's HTTP endpoint, Supavisor's admin endpoint and proxy listeners, and Logflare's gRPC server previously had no bind-address setting and listened on every interface. One opt-in env var now pins each to loopback, which is the missing piece for no-Docker native CLI stacks on a laptop or a shared host.
clickhouse: store NULL arrays as empty arrays supabase/etl
ClickHouse has no nullable arrays, so a top-level Postgres NULL array could not encode and stopped replication for every table in the pipeline. A NULL array now lands as an empty array, so NULL and empty become indistinguishable on the ClickHouse side while NULL elements inside an array survive.
clickhouse: store timestamp columns as UTC supabase/etl
Postgres timestamp columns mapped to a ClickHouse type with no time zone, so readers saw shifted values and filtering on the original value returned nothing. They now map to DateTime64(6, 'UTC') with timestamptz, which means existing rows written under the old mapping may not match.
fix(snowflake): bound CDC encoder memory across tables supabase/etl
Snowflake CDC held one row-batch builder per active table until a batch or schema boundary, and with many tables even small rows retained hundreds of zstd compressors. Events are now grouped by table inside existing Relation and TRUNCATE boundaries and finished one table at a time.
feat(cli): upgrade pg-delta to 1.0.0-alpha.57 (#7020) supabase/cli
The CLI bundles @supabase/pg-delta@1.0.0-alpha.57 and @supabase/pg-topo@1.0.0-alpha.8, and an unchanged declarative export no longer causes db declarative sync to revoke column grants. If you scripted around those spurious revokes, that workaround can go.
chore: PG19beta1 compatibility and CI supabase/supautils
supautils builds with -std=gnu11, fixes the timezone check hook for the PG 19 GUC struct layout, and adds PG 19 to CI. pg_tle has no release with PG 19 support yet, so CI builds it from a pinned main commit.
studio 2026.10.05-sha-94b8b06-r0 supabase/slim-services
Alongside: smoke-tested studio runtime artifacts published for linux/amd64, linux/arm64, and darwin/arm64, vulnerable transitive dependencies bumped in one commit per package, and the auto region selection experiment cleaned up so its ConfigCat flag can be removed.
$ ls supabase/week/ # the briefings behind this review
Keep up with Supabase in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.
Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.