RepoJournal
Supabase

@supabase

The open-source Firebase alternative powering thousands of startups

What actually shipped in Supabase, written up every day — commits, pull requests, releases, and security advisories.

One email a day. Unsubscribe in one click.

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

CLICKHOUSE SCHEMA CORRUPTION FIX LANDS ACROSS ETL STACK

By RepoJournal · Filed · About Supabase

Supabase shipped a critical fix that prevents ClickHouse from destroying newer columns during CDC replay restarts, then propagated the same safety logic across Pulumi and Terraform tooling.

The ETL team closed a data loss vulnerability where replayed relation events with stale schema snapshots drove backwards DDL, dropping columns that had been added since the last snapshot [1]. This is a guard rail every data pipeline operator needs: reject any snapshot older than what's already applied, and tell the operator exactly what happened [3]. The fix shipped alongside BigQuery client updates [2] and error message improvements [4] to make recovery paths clearer when schema mismatches occur. Across infrastructure tooling, a coordinated wave landed Apache 2.0 license alignment [9], [10], [13], and a systematic propagation of tag prefix handling into actual measurement tags rather than just description prefixes [8], [11], [14], [15]. The terraform-provider-ripe-atlas shipped v0.1.3 [12] with all these fixes baked in. On the docs and platform side, FGA permissions now read from the proper OpenAPI extension field [5], vulnerable dependencies got bumped [6], and broken local links in documentation went through systematic repair [7].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] clickhouse: Prevent unsafe schema rewind during CDC replay ↗ supabase/etl
  2. [2] feat(bigquery): Use updated BigQuery client ↗ supabase/etl
  3. [3] clickhouse: Prevent unsafe schema rewind during CDC replay (#925) supabase/etl
  4. [4] fix(clickhouse): Reword recovery snapshot error (#928) supabase/etl
  5. [5] fix: read FGA permissions from openapi spec x-fga-permissions extension (#48181) supabase/supabase
  6. [6] chore: Bump vulnerable deps (#48178) supabase/supabase
  7. [7] fix(docs) Fix local broken links (#48212) supabase/supabase
  8. [8] feat: add tagPrefix to measurement as a tag (#6) supabase/pulumi-atlas
  9. [9] fix: change to apache 2.0 license (#7) supabase/pulumi-atlas
  10. [10] fix: appropriate license ↗ supabase/terraform-provider-ripe-atlas
  11. [11] feat: plumb tag_prefix through to measurement tags (#9) supabase/terraform-provider-ripe-atlas
  12. [12] v0.1.3 ↗ supabase/terraform-provider-ripe-atlas
  13. [13] fix: switch to Apache 2.0 ↗ supabase/atlasctl
  14. [14] fix: tag -> namespace (#30) supabase/atlasctl
  15. [15] fix: store the tag prefix as a tag itself (#28) supabase/atlasctl

Quick answers

What shipped in Supabase on July 23, 2026?
Supabase shipped a critical fix that prevents ClickHouse from destroying newer columns during CDC replay restarts, then propagated the same safety logic across Pulumi and Terraform tooling. In total, 47 commits, 47 pull requests, and 1 releases landed.
Who contributed to Supabase on July 23, 2026?
9 developers shipped this update, including jmqd, iambriccardo, Hieu, Ivan Vasilov, Miranda Limonczenko, claude[bot], Charis, and davidbirdsong, and 1 more.
What were the notable Supabase updates?
clickhouse: Prevent unsafe schema rewind during CDC replay, feat(bigquery): Use updated BigQuery client, and clickhouse: Prevent unsafe schema rewind during CDC replay (#925).

More from @supabase

Daily updates, in your inbox

Follow Supabase

What actually shipped in Supabase, written up every day — commits, pull requests, releases, and security advisories.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?