Config tooling matures across the serverless Postgres stack

Config becomes a first-class citizen at Supabase

Supabase's CLI spent the week rethinking how project configuration moves between local and hosted environments. Config push is now diff-first, sending only partial updates instead of full overwrites, and a new config pull command brings remote state back down, with diffProjectConfig exported from the public entrypoint. A companion config diff command landed alongside a fix aligning the pgdelta format_options example with its 180 default, while a separate release trimmed the config public surface and added a compiled build. The same diff/pull work surfaced in the 3.0 beta line, which also retired push-capability pruning from ProjectConfig and corrected its hosted-field coverage.

Workers got most of the remaining attention. Commands moved under an experimental parent, then gained exposure control and a new --instances flag for setting instance count, plus a unified output shape across the command family and prompting for a worker name when one isn't provided. For local development, the CLI now injects the function slug into served functions, warns when PowerShell mangles piped dumps, and reads stdin on demand rather than eagerly.

Several fixes target migration and provisioning correctness: the CLI no longer skips schemas that collide with reserved names, skips DDL against provisioned ledgers, and accepts sbp_v0 login tokens it previously rejected. pg-delta plans got strategy-driven parallel shadow provisioning, with shadow baseline cache now on by default and an opt-out for teams that don't want it. Config release automation now requires a baseline config-v* tag before cutting a release.

Supabase's client SDK fills in realtime and storage gaps

The JS client SDK shipped a run of small but useful additions. Realtime can now wait for Postgres changes, letting code pause until a specific change event fires. PostgREST clients gained a getOpenApiSpec() method for fetching the API spec. Storage picked up bucket lifecycle configuration for automated policy management, and auth now unenrolls the unverified factor after a failed registration, a release that also patched high-severity browserslist advisories. Schema passed outside db options now triggers a warning rather than silence.

Neon goes to Europe and ships agent tooling

Neon's backend — Object Storage, Functions, and AI Gateway — is now available in AWS Europe (Frankfurt) in beta, alongside the existing US East region, with new AI Gateway models and a leaner neon init that writes function invocation URLs during env pull. The bigger developer-facing launch is @neon/tools, which wraps the Neon SDK into Zod-validated typed agent tools with adapters for MCP, Mastra, and Eve.

PlanetScale opens up replicas and webhook auth

The PlanetScale CLI added read-only replica CRUD commands, including replica selection for Postgres restores, plus a webhook authorization token option and a --db-name flag for Postgres psql sessions. On the platform side, webhooks now accept a configurable Authorization header sent unchanged with every delivery — useful for webhook-triggered automations that need to authenticate.