The Wire · Showcase
SWIFT SDK HARDENS CRYPTO, ETL OVERHAULS REPLICATOR RESOURCES, STUDIO SHIPS AI SUPPORT SYNC
By RepoJournal · Filed · About Supabase
Swift 2.51.0 tightens RSA JWK verification while the ETL API reworks its Kubernetes resource model for cleaner config and guaranteed QoS qualification.
Swift 2.51.0 [1] lands with hardened RSA JWK verification against malformed keys [1] and a critical realtime fix: httpSend() now supports per-event broadcast URLs with binary data, closing a gap in the real-time messaging layer. The Swift team is also deep in a repo-wide XCTest to Swift Testing migration [2], starting with the lowest-risk targets to validate the mechanical pattern before tackling Mocker-heavy phases [3]. On the ETL side, three related PRs reshape how replicator resources work: the API now derives sidecar and replicator limits from request values to help pods hit Kubernetes Guaranteed QoS [4], centralizes restart logic across all pipeline mutation endpoints [5], and reworks the config type hierarchy for clarity [6]. The docs desk shipped SDK reference updates for Dart and Swift stable releases [7], improved custom schema discoverability [8], and fixed a layout regression on the homepage Postgres card [9]. Studio's support form now syncs AI assistant conversations to Front in real time, giving your support team full context the moment a ticket arrives [10]. Security: ETL patched Rust dependencies [11] and shared-types bumped js-yaml to 4.3.0 [12].
Action items
- → Update supabase-swift to 2.51.0 before next release if you use realtime broadcast supabase/supabase-swift [plan]
- → Review ETL resource config changes if you maintain replicator pipelines supabase/etl [plan]
- → Patch ETL dependencies (Rust security fixes) supabase/etl [immediate]
References
- [1] v2.51.0 ↗ supabase/supabase-swift
- [2] test(supabase): migrate SupabaseTests to Swift Testing (Phase 0 pilot) ↗ supabase/supabase-swift
- [3] test(helpers): migrate HelpersTests to Swift Testing (Phase 1) ↗ supabase/supabase-swift
- [4] ref(api): Use requests == limits for better QoS class ↗ supabase/etl
- [5] feat(api): Improve handling of replicators and restarts ↗ supabase/etl
- [6] ref(api): Rework how replicator resources are done ↗ supabase/etl
- [7] docs: Update documentation from Dart, and Swift SDK changes ↗ supabase/supabase
- [8] docs: improve discoverability of custom schemas documentation (#42634) supabase/supabase
- [9] fix(www): postgres card art overlaps text column (#47734) supabase/supabase
- [10] feat: Support Form - Sync AI assistant conversation to Front ↗ supabase/supabase
- [11] fix(deps): Resolve security audit failures (#885) supabase/etl
- [12] chore(deps-dev): bump js-yaml from 4.1.1 to 4.3.0 in the npm_and_yarn group across 1 directory ↗ supabase/shared-types
FAQ
- What changed in Supabase on July 9, 2026?
- Swift 2.51.0 tightens RSA JWK verification while the ETL API reworks its Kubernetes resource model for cleaner config and guaranteed QoS qualification.
- What should Supabase teams do about it?
- Update supabase-swift to 2.51.0 before next release if you use realtime broadcast • Review ETL resource config changes if you maintain replicator pipelines • Patch ETL dependencies (Rust security fixes)
- Which Supabase repositories shipped on July 9, 2026?
- supabase/supabase-swift, supabase/etl, supabase/supabase, supabase/shared-types