Releases Index

BetaWeekly digests are a beta — we're trying something new. Feedback welcome.

The CLI becomes the control plane for serverless Postgres

August 24–30, 2026

NeonPlanetScaleSupabase
Neon, PlanetScale, Supabase

Neon renamed its CLI to `neon` and rebuilt it around branch-first workflows and read-only Postgres diagnostics, while PlanetScale pushed a wave of Insights, billing, and org commands into `pscale` and Supabase's CLI grew a full workers deployment surface.

The CLI becomes the control plane

Neon's biggest move of the week was a rebrand and a rethinking: the Neon CLI now installs as neon rather than neonctl (the old name survives as an alias), and the new command set is organized around branch-first workflows — link, checkout, and env pull — plus read-only Postgres diagnostics through inspect db, alongside api-keys and profile management. Agent onboarding landed too: neon mcp, neon skills, and neon plugins install Neon into coding agents like Cursor and Claude Code without hand-editing config, and the MCP server's inspect_database tool now flags queries stalled past 30 seconds. Behind the CLI work, Neon published a storage deep dive arguing that Postgres' write-ahead log should be the source of truth, backed by S3 and addressed by LSN — the same timeline primitive that makes branching and point-in-time restore cheap.

PlanetScale fills out the pscale surface

PlanetScale shipped a large batch of CLI and MCP work, and the throughline is that almost everything you used to do in the dashboard is now scriptable. Branching gained point-in-time restore when creating a PostgreSQL branch, via a new --restore-point flag, plus commands to list and show switchovers for a branch and to list available regions and configured Vitess read-only regions. Restore flows got simpler overall: payment-method show, update, and delete arrived, and --restore no longer demands --from/--to.

Organization administration is now terminal-native: org billing and role settings, plus team and team-member management, SSO enablement through pscale org sso with domain verification and IdP role flags, paginated invoice listing, payment-method updates that hand off to Stripe Checkout, and service-token lookup by ID. Backup protection is settable from the CLI now — protected backups can't be deleted until protection is lifted — and a single release bundled Insights query inspection, billing invoices, backup protection, and org team management together.

The MCP server is where the most interesting capability landed: it can now read query tags from Insights to attribute load and latency to an app, route, job, or user, group failing queries by error fingerprint and drill into individual failed executions, and pull Postgres branch server logs filtered by level, time range, role, or LogsQL. On the CLI side, pscale metrics gained dedicated commands for query patterns, table storage, tablet series, and tag sets, and Insights gained query samples, show, summary, and traffic-budget commands plus single schema recommendations with ready-to-apply DDL. The Postgres metrics page was reorganized into per-node tabs with shareable URLs.

Supabase builds out workers and tightens local dev

Supabase's CLI week was dominated by a new deployment primitive: workers. Scaffolding, deploying, and managing them arrived in quick succession — workers new to scaffold, workers push to deploy, and workers list, status, and delete to manage them — with a [workers] section added to the project config schema. Configuration itself got more formal: defaults are exposed with sparse mapping functions, and a hosted ProjectConfig subset defines which options hosted projects actually support.

Local development got faster and less flaky. The shadow database baseline is now cached as a PGDATA snapshot instead of rebuilt on every migration run, dead database connections are detected rather than left stale, and piped stdin buffering is bounded while start wrappers exec so docker stop no longer stalls for ten seconds. Kong's DNS cache TTLs are capped, external scope targets mount correctly, and the config default for auto_expose_new_tables now matches the platform — a change that also carried into the stable release. Internally, the stack's remote runtime moved to Effect RPC and pg-delta upgraded to alpha.46.

In the client SDK, Supabase JS fixed a stolen-lock AbortError and an unhandled refresh rejection, and began warning on the deprecated lock option, with the same auth fixes landing on the canary channel.

AI-generated digests may contain mistakes.
Releases covered37
PlanetScale
Supabase