The Wire · Showcase
CLI FIXES TIMESTAMP BUG BLOCKING EVERY PROJECT LINK
By RepoJournal · Filed · About Supabase
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.
The Management API was serializing timestamps with numeric UTC offsets, but the generated client schemas were pattern-matching Z-anchored ISO 8601 strings, causing validation failures on every API call [1][2]. The fix drops pattern validation during code generation, letting date-time strings rely on their format annotation alone [2]. This same release also surfaces staging errors in serve instead of suppressing them [1], and continues the TypeScript migration with db reset, gen bearer-jwt, and shell completion now running on the TypeScript shell. Over on the Studio side, role-aware access checks are now in place for scoped token creation, letting the UI properly guide users toward project-scoped tokens when appropriate [3]. Eval results refreshed from the latest automated run [4].
One email a day. Unsubscribe in one click.
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. Read a past issue →
Action items
- → Upgrade supabase CLI to v2.113.0 immediately supabase/cli [immediate]
- → Test supabase link and branches list commands to confirm connectivity restored supabase/cli [immediate]
- → Review scoped token UX changes in Studio during next auth review supabase/supabase [plan]
References
- [1] v2.113.0 ↗ supabase/cli
- [2] fix(api): accept offset timestamps ↗ supabase/cli
- [3] feat(studio): role-aware access feedback in scoped token creation ↗ supabase/supabase
- [4] chore: refresh eval results ↗ supabase/evals