Releases Index

Serverless Postgres

Managed Postgres with scale-to-zero and branching for modern stacks.

This week's digestSep 14 – 20, 2026

Neon's whole backend goes GA as Postgres platforms race on search and branching

Neon's backend reached general availability, turning serverless Postgres into a full branchable stack of storage, auth, functions, and an AI gateway, while PlanetScale shipped a fast full-text search extension for Postgres and attached existing MySQL databases to Vitess as external keyspaces.

Read the digest59 releases covered
Week of Sep 21in progress · digest Monday
FriSep 25, 20262 releases
Supabase
Daily summary

Supabase CLI adds project pull and stack management

Supabase CLI gained a supabase pull command that sets up a full local environment from a remote project plus experimental stack commands, while Supabase JS fixed a type-instantiation failure on large relationship unions.

  • Supabase CLI can now pull a complete local setup from a remote project with supabase pull, and adds experimental stack start, stop, status, list, logs, prepare, and restart commands
  • Supabase CLI startup hangs on macOS state publication, Docker daemon stalls that blocked db start, and large SQL blocks stalling db reset are fixed, and gen types no longer needs Docker
  • Supabase JS resolves instantiation depth errors in PostgREST types when working with large relationship unions
CLIv2.118.0
Client SDKv2.117.2
ThuSep 24, 20263 releases
NeonPlanetScale
Daily summary

Neon plans native realtime sync as Prisma 8 nears release

Neon outlined plans to build a realtime sync service natively into its platform, while Prisma's v8 release candidate introduced Postgres full-text search and a rewritten schema contract.

  • Neon is planning a native realtime and sync service built into its platform and Lakebase, aimed at scale-to-zero and branching support
  • Prisma's v8 release candidate adds Postgres full-text search, prepared ORM reads and aggregates, multi-file schemas, and a documented path from Prisma 7 to 8, though schema files now require a `// use prisma-8` header and lose `dbgenerated(...)`
  • PlanetScale database-js v2.0.0 removed parameter interpolation and now requires Node 22
  • Supabase JS fixed instantiation depth errors when querying large PostgREST relationship unions

Branch reset now reverts Object Storage too

Reset from parent now rolls back a branch's Object Storage buckets and objects to the parent's current state along with its Postgres data, reverting uploads, overwrites, and deletes made on the branch, in AWS US East (Ohio) and AWS Europe (Frankfurt). Lakebase Search extensions lakebase_vector 1.1.1 and lakebase_text 0.1.3 ship performance improvements and fixes.

Details

Realtime and sync coming natively to Neon

Interview with Electric co-founder James Arthur describes plans to build a next-generation realtime sync service natively into Neon and Lakebase, with native support for scale-to-zero and branching. The team aims to solve the expressiveness-versus-performance tension that makes realtime sync fail in production on Postgres, following Neon's backend GA.

Details
Electrifying Neon: building the realtime backend
PlanetScale database-jsv2.0.0
WedSep 23, 20263 releases
PlanetScaleSupabase
Daily summary

Supabase CLI adds build-context exclude patterns

Supabase CLI gained exclude patterns for compute build contexts and Client SDK fixed a cross-tab token refresh race, while PlanetScale hardened placeholder parsing in database-js.

  • Supabase CLI now supports exclude patterns when defining the compute build context, so builds can skip specified files (config v0.10.0)
  • Supabase Client SDK returns the stored session when a token refresh loses a race to another tab, preventing the losing tab from dropping into a logged-out state
  • PlanetScale database-js hardened placeholder sanitization and cleared outstanding npm audit warnings via an undici update
PlanetScale database-jsv1.20.2
CLIconfig-v0.10.0
Client SDKv2.117.1
TueSep 22, 20262 releases
SupabaseNeon
Daily summary

Neon adds object-storage triggers as Supabase turns on passkeys

Neon Functions can now be invoked automatically when a file lands in an Object Storage bucket, while Supabase's client SDK enabled its passkey auth API by default and deprecated the experimental opt-in.

  • Neon added a storage_object_created trigger that runs a Neon Function when an object is uploaded, passing the bucket name and object key and optionally scoping to a key prefix, while staying compatible with scale to zero.
  • Supabase's JS client SDK now enables the passkey API by default, deprecating the experimental opt-in and forwarding the mediation option to navigator.credentials.get in signInWithPasskey.
Client SDKv2.117.0

Object Storage uploads can now invoke Neon Functions

A new storage_object_created trigger invokes a Neon Function when an object is created in an Object Storage bucket, passing the bucket name and object key in the POST body and supporting an optional key prefix to scope it to a path. Functions are long-running and remain compatible with scale to zero, and the schedule trigger is also available.

Details
Mike Jerome
MonSep 21, 20263 releases
PlanetScaleNeon
Daily summary

Neon Functions gain schedule triggers and custom domains

Neon made Function Triggers generally available so branch-scoped cron schedules can invoke deployed functions without waking Postgres compute, and added custom domains with automatic TLS for its Functions — the only user-facing changes on a day otherwise dominated by Supabase release-candidate churn.

  • Neon Function Triggers let a branch-scoped cron schedule invoke a deployed Function while scale to zero stays on, with triggers running JavaScript or TypeScript that can reach HTTP, Object Storage, and the AI Gateway; child branches inherit parent triggers disabled until enabled.
  • Neon Functions custom domains reached GA, replacing the Neon invocation URL with a branded hostname registered from the Console, CLI, SDK, or API and tied to one Function on one branch, with Let's Encrypt TLS provisioned automatically.
  • PlanetScale CLI extension commands now pick up profile updates instead of relying on the previous profile handling.
PlanetScale CLIv0.338.0

Neon Blog

2 updates

Neon Functions now support custom domains, replacing the Neon invocation URL with a branded hostname registered from the Console, CLI, SDK, or API. Domains are attached to one Function on one branch, and TLS certificates are provisioned automatically through Let's Encrypt.

Details
Custom domains for Neon Functions

Function Triggers let a branch-scoped cron schedule invoke a deployed Neon Function, keeping the timer outside the Postgres compute so scale to zero can stay on, unlike pg_cron. Triggers run JavaScript or TypeScript that can call HTTP, Object Storage, and the AI Gateway, and child branches inherit parent triggers disabled until enabled.

Details
Your Neon Functions can now run on a schedule
Week of Sep 147 releases
DigestNeon's whole backend goes GA as Postgres platforms race on search and branchingRead →
FriSep 18, 20266 releases
PlanetScaleTurso
Daily summary

PlanetScale expands Vitess with external keyspaces and per-shard sizing

PlanetScale made external MySQL keyspaces queryable through Vitess without data import, added per-shard VTTablet sizing and by-name Neki extension management, and patched a SQL injection flaw in the CLI's D1 import parser, while Supabase's Auth and CLI churn was limited to release candidates and checksum-only builds.

  • PlanetScale now attaches an existing MySQL database as an external keyspace on a Vitess production branch, queryable through Vitess without importing data first, via the Clusters page or pscale keyspace create-external.
  • Vitess keyspaces can now size VTTablet resources per shard, so a single shard can get more CPU, memory, or Metal local storage without resizing the whole keyspace and without changing key ranges, VSchema, or routing.
  • Neki extensions can be enabled by name and configured with parameters in one Terraform or pscale update, though extensions can no longer be combined with shared_preload_libraries or session_preload_libraries.
  • The PlanetScale CLI fixes a SQL injection vulnerability in D1 import CHECK expression parsing.

PlanetScale Changelog

3 updates

An existing MySQL database can now be attached as an external keyspace on a Vitess production branch, with PlanetScale running an external tablet against that source so it can be queried through Vitess without importing data first. External keyspaces can be created from the Clusters page on production branches or via the pscale keyspace create-external CLI command.

Details

Neki extensions can now be enabled by name and configured with parameters in a single Terraform or pscale CLI update, with the extension list replacing the currently enabled set. Existing configurations that set preload libraries directly still work, but extensions cannot be combined with shared_preload_libraries or session_preload_libraries.

Details

VTTablet sizes can now be adjusted for individual shards in a Vitess keyspace, enabled from the keyspace Shards tab, letting a single shard get more CPU, memory, or Metal local storage without resizing the whole keyspace. Unchanged shards keep the keyspace default, and enabling it does not alter key ranges, VSchema, or routing.

Details
libSQLv0.6.0-pre.42
ThuSep 17, 20261 release
Neon
Daily summary

Neon ships a complete backend stack for agent-built apps

Neon made its Lakebase Postgres, Object Storage, Functions, Managed Better Auth, and AI Gateway generally available as composable backend primitives, while PlanetScale open-sourced the Lead full-text search extension for Postgres testing and Supabase's canary SDK forwarded the mediation option to passkey sign-in.

  • Neon's Lakebase Postgres, Object Storage, Functions, Managed Better Auth, and AI Gateway are now GA, packaged as composable primitives on standard interfaces so agents can assemble full backends.
  • PlanetScale released Lead, an open-source Postgres full-text search extension for CI, dev, and staging use, noting it slows past a few MB of indexed text and directing production workloads to TIN.
  • Supabase's client SDK now passes the mediation option through to navigator.credentials.get in signInWithPasskey.

Neon backend GA: storage, auth, functions all branch

Neon's backend is now generally available, extending branching beyond Postgres so every PR, preview, or agent session gets a full copy of the schema, object storage, auth, and functions. The release adds Function Triggers for schedules and object-created events, plus a declarative neon.ts config applied with neon deploy.

Details