Fixes & improvements
- API: Enabled checking for the Neon API specification to ensure that examples are updated when the specification is modified.
- API: Added a
history_retention_seconds
property to the Project response body. Neon retains a 7-day history to support point-in-time restore. History retention will become a configurable parameter in a future release. - API: Increased the maximum value of the
suspend_timeout_seconds
property in the Endpoint API from 86400 seconds (1 day) to 604800 seconds (7 days). This change affects the maximum scale to zero setting that Neon Pro plan users can configure when creating or editing a compute endpoint. The scale to zero setting defines the number of seconds of inactivity after which a compute endpoint is automatically suspended. The default is 300 seconds (5 minutes). For more information, see Scale to zero configuration. - Control Plane: Added a constraint to ensure that the maximum autoscaling compute size is greater than or equal to the minimum compute size.
- UI: Redesigned the branch details page in the Neon Console. In addition to the information displayed previously, the page now provide usage metrics, including Active time, Compute time, Written data, and Data transfer. This information enables you to monitor usage for individual branches. Refer to our Billing page for information about the usage metrics. The compute endpoint information on the branch details page has also been expanded to include Compute size, Scale to zero delay, and Last active information. Compute size (min) and Compute size (max) values are shown for computes with the Autoscaling feature enabled. For information about these values, see View a compute endpoint.
- UI: Added an Active time column to the table on the Branches page in the Neon Console. This column shows the number of hours the branch compute endpoint has been active for the current month.
- UI: The Connection Details dialog displayed when creating a project or a branch now provides Pooled connection and Direct connection tabs, allowing you to copy a pooled or direct connection string for the ready-to-use
neondb
database. For information about connection pooling in Neon, see Connection pooling. - UI: Updated the
prisma.js
code example accessible from the Connection Details widget on the Neon Dashboard. The connection string now includes aconnect_timeout
parameter to prevent Prisma from timing out due to cold starts, and apgbouncer=true
parameter, which is required when using Prisma with a pooled connection string. For more information about using Neon with Prisma, see Connect Neon to Prisma. - UI: Added icons and hover help to the Usage widget on the Neon Console.
Support for the US East (N. Virginia) region
Added support for the US East (N. Virginia) — aws-us-east-1
region. For more information about Neon's region support, see Regions.
Postgres extension support
Added support for the ip4r
and pg_hint_plan
extensions. For more information about Postgres extensions supported by Neon, see Postgres extensions.
Fixes & improvements
- Compute: Added support for
lz4
andzstd
WAL compression methods. - Compute: Added support for
procps
, which is a set of utilities for process monitoring. - Pageserver: Implemented
syscalls
changes in the WAL redoseccomp
(secure computing mode) code to ensure AArch64 support.
Documentation updates
- Added a guide for using Grafbase Edge Resolvers with Neon. The guide describes how to create a GraphQL API using Grafbase and use Edge Resolvers with the Neon serverless driver to access your Neon database at the edge.
- Added a guide for using WunderGraph with Neon. WunderGraph is an open-source Backend for Frontend (BFF) framework designed to optimize developer workflows through API composition. The guide describes how you can use WunderGraph with Neon to accelerate application development.
- Added Segment to the list of applications and clients that support connecting to Neon. See Tested applications and IDEs.
- Added a topic describing how to connect to Neon securely. See Connect to Neon securely.