Who contributed to Supabase on August 12, 2026?

11 developers shipped this update, including David_C, joshenlim, charislam, aantti, kemal.earth, supabase-evals-releaser, supabase-evals-releaser[bot], and Jordi Enric, and 3 more.

What were the notable Supabase updates?

feat!: use DateTime for all timestamp fields, fix(supabase_flutter)!: persist the session with SharedPreferencesAsync, and refactor(gotrue)!: drop the pre-2024-01-01 API version fallbacks.

@supabase

The open-source Firebase alternative powering thousands of startups

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

FLUTTER SDK BREAKS: DATETIME EVERYWHERE, GOTRUE DROPS LEGACY API FALLBACKS

By RepoJournal · Filed 06:58 UTC on August 12, 2026 · About Supabase

11 people shipped this

spydon @spydon 3 cited

Coly010 @Coly010 2 cited

joshenlim @joshenlim 1 cited

charislam @charislam 1 cited

aantti @aantti 1 cited

Jordi Enric @jordienr 1 cited

David_C @YuDavidCao

kemal.earth @kemaldotearth

supabase-evals-releaser @supabase-evals-releaser

supabase-evals-releaser[bot] @supabase-evals-releaser[bot]

jgoux @jgoux

Supabase Flutter ships three breaking changes at once: all timestamps are now DateTime objects, session storage moves to SharedPreferencesAsync, and GoTrue kills pre-2024 API version negotiation.

The Flutter SDK's timestamp overhaul [1] replaces raw ISO strings and Unix ints with parsed DateTime objects across Session, User, and Auth types, forcing a compile-time migration for any code reading `expiresAt`, `createdAt`, or confirmation timestamps. This ships alongside a critical session persistence fix [2] where the default storage now uses the async SharedPreferences API instead of the legacy one, preventing session loss on Windows and Linux when apps have already migrated their own code. A third breaking change [3] removes GoTrue's runtime API version sniffing and the error-parsing fallbacks it drove, cleaning up two years of compatibility shims and bringing the SDK in line with a 2024-01-01 API cutoff that's already been enforced server-side. On the platform side, the main repo ships a doc overhaul for diagnosing stuck and blocked queries [4], notebook read tools for the AI agent [5], and flips Envoy to the default API gateway in self-hosted setups now that Kong's OSS line is frozen [6]. CLI work continues its Go-to-TypeScript port with functions download [8] completed and v2 Management API namespace support added [9]. Agent skills gains a structured debugging workflow [7] that gives developers an evidence-first troubleshooting loop instead of guessing.

Action items

→ Pin Flutter SDK version before updating; review all DateTime field access in auth and session code supabase/supabase-flutter [immediate]
→ Test session persistence on Windows/Linux if using Supabase.initialize defaults supabase/supabase-flutter [plan]
→ Update self-hosted deployments to use Envoy as the new default gateway supabase/supabase [plan]
→ Review new query diagnostics docs for connection troubleshooting patterns supabase/supabase [monitor]

References

[1] feat!: use DateTime for all timestamp fields ↗ supabase/supabase-flutter
[2] fix(supabase_flutter)!: persist the session with SharedPreferencesAsync ↗ supabase/supabase-flutter
[3] refactor(gotrue)!: drop the pre-2024-01-01 API version fallbacks ↗ supabase/supabase-flutter
[4] Add docs for diagnosing stuck and blocked queries ↗ supabase/supabase
[5] feat(studio): notebook read tools ↗ supabase/supabase
[6] feat(self-hosted): envoy is the default api gateway ↗ supabase/supabase
[7] feat(supabase): add debugging workflows to the supabase skill (#112) supabase/agent-skills
[8] fix(cli): port functions download to native TypeScript (CLI-1963) ↗ supabase/cli
[9] feat(api): support v2 namespace endpoints in @supabase/api ↗ supabase/cli

Quick answers

What shipped in Supabase on August 12, 2026?: Supabase Flutter ships three breaking changes at once: all timestamps are now DateTime objects, session storage moves to SharedPreferencesAsync, and GoTrue kills pre-2024 API version negotiation. In total, 42 commits, 43 pull requests, and 2 releases landed.
Who contributed to Supabase on August 12, 2026?: 11 developers shipped this update, including David_C, joshenlim, charislam, aantti, kemal.earth, supabase-evals-releaser, supabase-evals-releaser[bot], and Jordi Enric, and 3 more.
What were the notable Supabase updates?: feat!: use DateTime for all timestamp fields, fix(supabase_flutter)!: persist the session with SharedPreferencesAsync, and refactor(gotrue)!: drop the pre-2024-01-01 API version fallbacks.

SUPABASE SHIPS MCP DEBUGGING TOOLS AND PORTS CLI TO TYPESCRIPT

Self-hosted deployments gain query logging for AI-assisted debugging while the CLI sheds its final Go dependencies.

javascript 77 shipped

@supabase Aug 11

NOTEBOOKS DATA LAYER SHIPS; CLI COMPLETES GO MIGRATION

Supabase locked in the core notebooks API boundary and query hooks while the CLI finally finished porting its last Go seams to TypeScript.

javascript 46 shipped

@supabase Aug 10

SUPABASE EVALS PIPELINE REFRESHED WITH LATEST BENCHMARK RESULTS

Supabase refreshed its eval results dataset from the latest automated run, keeping benchmark data current across the platform.

javascript 2 shipped

@supabase Aug 9

CLI FIXES TIMESTAMP BUG BLOCKING EVERY PROJECT LINK

Supabase CLI v2.113.0 shipped overnight with the fix for the offset timestamp parsing error that broke supabase link and branches list across all projects.

javascript 8 shipped

Elsewhere on the wire

AI Agents Aug 13

ANTHROPIC INTEGRATION FIXES TOOL BLOCKS, OPENHANDS UNBLOCKS CI, CLINE PATCHES COMPOSER WEDGE

LangChain's Anthropic integration corrected tool result handling and model profiles [ref:1], while OpenHands fixed a critical test infrastructure failure blocking all PRs and shipped 1.13.0 with conversation archives [ref:6][ref:9].