RepoJournal
Supabase

@supabase

The open-source Firebase alternative powering thousands of startups

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

One email a day. Unsubscribe in one click.

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

SUPABASE HARDENS ANALYTICS SQL AGAINST INJECTION ATTACKS

By RepoJournal · Filed · About Supabase

A three-part security refactor shipped overnight to prevent SQL injection in BigQuery and ClickHouse analytics queries, closing a compile-time safety gap across the entire logs pipeline.

Supabase landed the final piece of its safe-analytics-sql series, with all three PRs now merged [1] [2] [3]. The work introduces a compile-time safety model for analytics queries that previously lacked protection against untrusted input from URL parameters and other sources. ServiceFlow.sql.ts got branded with SafeLogSqlFragment [3], completing the wire-boundary wrapper that now shields all five unified-logs query hooks [2] from direct interpolation risks. On the UI side, the team finished migrating deprecated Modal components out of Organization settings [4], swapping them for Dialog across subscription downgrade flows, OAuth app management, and member limit alerts. A smaller type-safety win landed in core: removing any-type annotations to let ratchet rules pass [5]. Over in realtime, supabase-js bumped to v2.106.2 [6], restoring signup user response and adding Hermes-safe React Native exports. Dashboard also got an IPv6 DNS connection fix [7] for tenant migrations, addressing a timing issue on disconnect [8], with the realtime service now at v2.98.3 [9].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] feat: add safe SQL execution for analytics queries (BigQuery/ClickHouse) (#46287) supabase/supabase
  2. [2] feat(logs): route unified-logs hooks through executeAnalyticsSql (#46333) supabase/supabase
  3. [3] feat(logs): brand ServiceFlow.sql.ts with SafeLogSqlFragment (#46336) supabase/supabase
  4. [4] chore: migrate Organization settings `Modal` to `Dialog` (#46332) supabase/supabase
  5. [5] chore: remove any type to let ratchet rules pass (#46349) supabase/supabase
  6. [6] chore: update @supabase/supabase-js to v2.106.2 ↗ supabase/realtime
  7. [7] fix(dashboard): tenant db connect dns ipv6 (#1910) supabase/realtime
  8. [8] fix: timing issue on connection disconnect (#1908) supabase/realtime
  9. [9] v2.98.3 ↗ supabase/realtime

Quick answers

What shipped in Supabase on May 26, 2026?
A three-part security refactor shipped overnight to prevent SQL injection in BigQuery and ClickHouse analytics queries, closing a compile-time safety gap across the entire logs pipeline. In total, 30 commits, 28 pull requests, and 2 releases landed.
Who contributed to Supabase on May 26, 2026?
1 developer shipped this update, including supabase-libs-pr-manager[bot].
What were the notable Supabase updates?
feat: add safe SQL execution for analytics queries (BigQuery/ClickHouse) (#46287), feat(logs): route unified-logs hooks through executeAnalyticsSql (#46333), and feat(logs): brand ServiceFlow.sql.ts with SafeLogSqlFragment (#46336).

More from @supabase

Daily updates, in your inbox

Follow Supabase

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

or

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

Elsewhere on the wire

Want every project, not just this one?