111 wires and counting

$ follow Supabase

Keep up with Supabase in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

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.

$ status

wire 2026-09-03
stories 99

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

postgrest-typegen drops pg-format, fixes computed-field matching and trigger views

By RepoJournal · Filed · About Supabase

postgrest-typegen 0.2.1 ships fixes that reshape how it resolves computed fields and handles trigger views, while a dependency drop cleans up ESM consumption.

The PostgREST type generator is the busiest desk today. postgrest-typegen 0.2.1 [1] ships three fixes: computed fields are now matched by argument type rather than by string-comparing the function's `argument_types` against the relation name [2]; trigger-writable views and PG18 virtual generated columns got corrected handling [3]; and database values are properly escaped in Swift and Go string literals [1]. Separately, postgrest-typegen inlined a `literal()` port of pg-format@1.0.4 and dropped the `pg-format` and `@types/pg-format` dependencies [4][5]. pg-format is CommonJS-only, so its removal makes the package easier to consume from ESM and bundled CLIs like supabase/cli.

The studio and dashboard work focuses on observability and correctness. The sign-in page previously emitted only a pageview on entry and the success-side `sign_in` event on exit, so failed or abandoned attempts were invisible. It now fires an unsampled `sign_in_submitted` event at every initiation point and classifies failures via a new `signin` origin in `dashboard_error_created` [6]. A bug in the AI Assistant notebook-update preview where view-only cell edits (table ↔ chart, chart parameters) showed an empty diff was fixed by making the diff editor compare the full cell configuration, not just SQL text [7].

The replicator's resource configuration got simpler and more predictable [8]. CPU and memory now resolve independently, with startup requests using only pipeline overrides or API-wide defaults, and destination-specific resource defaults were removed. The API also consolidated eleven one-off helpers for required Kubernetes secret environment entries into one helper, adding the shared Postgres password entry once before destination-specific entries [9]. Meanwhile the etl-api now reuses canonical `Default` implementations instead of its own defaults [10].

The ETL API also removed its legacy StatefulSet lookup, using only the current StatefulSet name for deletion and existence checks while retaining legacy pod-status and reconciliation cleanup safeguards [11][12]. Elsewhere, Supabase published a new blog post, "Are Supabase docs agent-friendly? We didn't know, so we checked," which reports on an eval-driven audit of the docs [13]. The docs now include a reference section for the `@supabase/middleware` SDK with installation guides for npm, Yarn, pnpm, Deno, and Bun [14]. Worker log views, previously limited to the last 24 hours with no filtering, now support selectable time ranges, event-message search, and an HTTP-method filter applied in the analytics query and included in the cache key [15]. Routine regenerations landed for eval results [16] and MCP management API types [17].

Action items

References

  1. [1] chore(main): release postgrest-typegen 0.2.1 (#139) ↗ supabase/sdk
  2. [2] fix(postgrest-typegen): match computed fields by argument type, not name (#137) ↗ supabase/sdk
  3. [3] fix(postgrest-typegen): update-only trigger views, PG18 virtual generated columns, legacy metadata compatibility ↗ supabase/sdk
  4. [4] fix(postgrest-typegen): inline pg-format literal and drop the dependency (#138) ↗ supabase/sdk
  5. [5] fix(postgrest-typegen): inline pg-format literal and drop the dependency ↗ supabase/sdk
  6. [6] feat(studio): instrument sign-in attempts and failures ↗ supabase/supabase
  7. [7] fix(studio): display diff for view-only notebook cell edits ↗ supabase/supabase
  8. [8] ref(config): Improve resources config ↗ supabase/etl
  9. [9] ref(api): centralize required Kubernetes secret environment entries ↗ supabase/etl
  10. [10] ref(etl-api): reuse canonical pipeline config defaults ↗ supabase/etl
  11. [11] ref(api): remove legacy StatefulSet lookup ↗ supabase/etl
  12. [12] ref(api): remove legacy StatefulSet lookup (#1009) ↗ supabase/etl
  13. [13] Add blog post: Are Supabase docs agent-friendly? (#49800) ↗ supabase/supabase
  14. [14] docs: wire middleware sdk docs ↗ supabase/supabase
  15. [15] feat(workers): add log filters FE-4322 ↗ supabase/supabase
  16. [16] chore: refresh eval results ↗ supabase/evals
  17. [17] chore: regenerate management API types ↗ supabase/mcp

Quick answers

What shipped in Supabase on September 3, 2026?
postgrest-typegen 0.2.1 ships fixes that reshape how it resolves computed fields and handles trigger views, while a dependency drop cleans up ESM consumption. In total, 49 commits, 49 pull requests, and 1 releases landed.
Who contributed to Supabase on September 3, 2026?
14 developers shipped this update, including iambriccardo, farazdagi, supabase-evals-releaser, supabase-evals-releaser[bot], Nik Richers, mandarini, pamelachia, and charislam, and 6 more.
What were the notable Supabase updates?
chore(main): release postgrest-typegen 0.2.1 (#139), fix(postgrest-typegen): match computed fields by argument type, not name (#137), and fix(postgrest-typegen): update-only trigger views, PG18 virtual generated columns, legacy metadata compatibility.