Who contributed to Supabase on July 22, 2026?

11 developers shipped this update, including Leandro Pereira, ivasilov, Ana, joshenlim, dnywh, Utkarash Kumar Singh, Márton Boros, and imor, and 3 more.

What were the notable Supabase updates?

feat(www): add "Supabase Pipelines is now in Public Alpha" blog post (#47864), v2.119.0, and v2.118.0.

Jul 22, 2026

$ the-wire · showcase

PIPELINES HITS PUBLIC ALPHA, REALTIME SQUASHES RACE CONDITION

By RepoJournal · Filed 06:59 UTC on July 22, 2026 · About Supabase · Composed from the cited sources · methodology

11 people shipped this

realtime-release-bot[bot] @realtime-release-bot[bot] 2 cited

edgurgel @edgurgel 2 cited

ivasilov @ivasilov 1 cited

Ana @ana1337x 1 cited

Márton Boros @brainrake 1 cited

imor @imor 1 cited

github-actions[bot] @github-actions[bot] 1 cited

Leandro Pereira @leandrocp

joshenlim @joshenlim

dnywh @dnywh

Utkarash Kumar Singh @utkarash2991

Supabase Pipelines moves out of private alpha with full schema change support, while the realtime stack hardens against clustering edge cases.

In brief

Supabase Pipelines hits public alpha. native ETL for your Postgres database without leaving the dashboard. moving data between sources just got simpler.
Realtime v2.119 squashes a rare DOWN Census race condition. the kind of bug that only hits you in production at 3am on a Sunday.
Postgres fix: pg_net background worker now runs as postgres instead of supabase role. permissions were holding up network operations. now they're not.
Supabase Postgres 15.14.1.151 drops. minor version bump but worth the upgrade if you're on an earlier 15 build.
Realtime gains shutdown buttons for Connect and Postgres CDC RLS. manual kill switch when graceful shutdown won't cut it.

Supabase Pipelines is now in public alpha [1], bringing schema change support (add/remove/rename columns, nullability defaults) that developers have been waiting for. This is the upgrade path you've been building toward. Meanwhile, realtime shipped two releases overnight: v2.119.0 [2] fixes a rare race condition where stale node data persists after shutdown, and v2.118.0 [3] adds shutdown controls for Connect and Postgres CDC RLS in tenant info [4]. The race condition fix [5] specifically addresses a clustering bug where `:sync` messages from unknown peers could corrupt state; the team now ignores those and rediscovers periodically to avoid future races. On the studio side, ESLint enforcement just got stricter [6] with valtio and react-hook-form plugin rules, catching common API pitfalls at lint time instead of runtime. Documentation across supabase/postgres [7] and supabase/realtime schema got cleaned up (dead wiki links, stale references), plus postgres v15.14.1.151-x86 [8] shipped with the pg_net background worker now correctly running as the postgres user [9] instead of supabase_admin.

Action items

→ Review Pipelines public alpha docs and test schema changes in your deployment pipeline supabase/supabase [plan]
→ Upgrade realtime to v2.119.0 to patch the Census race condition supabase/realtime [plan]
→ Run lint checks if you use valtio or react-hook-form; new ESLint rules are now enforced supabase/supabase [monitor]

References

[1] feat(www): add "Supabase Pipelines is now in Public Alpha" blog post (#47864) supabase/supabase ↗
[2] v2.119.0 ↗ supabase/realtime
[3] v2.118.0 ↗ supabase/realtime
[4] feat: add shutdown btns to Connect and Postgres CDC RLS on tenant info ↗ supabase/realtime
[5] fix: rare DOWN Census race condition ↗ supabase/realtime
[6] chore(studio): add valtio and react-hook-form ESLint ratchet rules ↗ supabase/supabase
[7] docs: fix stale docs (dead wiki links, nix structure, migration-test and build examples) (#2286) ↗ supabase/postgres
[8] 15.14.1.151-x86 ↗ supabase/postgres
[9] fix: make pg_net background worker run as postgres ↗ supabase/postgres