Neon Deploy: Learn how Neon helps developers ship faster with Postgres. Grab your ticket

Changelog

The latest product updates from Neon

RSS feed

Read Replicas on the Free Plan

You may have seen the announcement earlier this week: Read replicas are now available in the Free Plan.

Add read replica

If you're not familiar Neon Read Replicas, you might be interested to know that we take a fundamentally different approach by leveraging our serverless architecture. In Neon, read replicas are independent compute instances designed to handle read operations on the same data as your primary read-write compute. There's no replication or copying of data involved, allowing you to create a read replica almost instantly with no additional storage cost.

Neon's Read Replicas support a variety of use cases, including:

  • Horizontal scaling
  • Analytics and ad-hoc queries
  • Read-only data access

To learn more about Neon Read Replicas, check out these docs and articles:

Postgres extension updates

We added support for several extensions to Postgres 17, including pgvector 7.4.

create extension pgvector

Now available on Postgres 17:

ExtensionVersion
hypopg1.4.1
pg_hint_plan1.7.0
pg_ivm1.9
pg_partman5.1.0
pg_uuidv71.6.0
pgvector7.4
pgtap1.3.3
plv83.2.3
rdkit4.6.0
timescaledb2.17.0
wal2json2.6

In addition, we updated the following extension versions on Postgres 14, 15, and 16:

ExtensionOld VersionNew Version
hypopg1.4.01.4.1
pg_ivm1.71.9
pg_partman5.0.15.1.0
pg_uuidv71.0.11.6.0
pgvector7.27.4
pgtap1.2.01.3.3
plpgsql_check2.5.32.7.11
wal2json2.52.6

For a complete list of Postgres extensions supported by Neon and upgrade instructions, see Postgres extensions.

Neon SQL Editor AI features are now open to everyone

The AI-driven features in the Neon SQL Editor we opened to Early Access users a few weeks ago are now available to everyone. In case you missed that announcement, here's what's new:

  • SQL generation: Convert natural language requests to SQL with ease. Press the ✨ button or use Cmd/Ctrl+Shift+M, type your request, and the AI assistant will generate the corresponding SQL. It’s schema-aware, so you can reference table names, functions, and other objects in your schema.
  • Fix with AI: When your query returns an error, click Fix with AI next to the error message. The AI assistant will analyze the issue, suggest a fix, and update the SQL Editor so you can run the query again.
  • AI-generated query names: Queries in the Neon SQL Editor's History are automatically assigned descriptive names. This feature helps you quickly identify and reuse previous queries.

To learn more, see Neon SQL Editor AI features.

Easier User to Org account conversion

We've introduced a new way to convert personal Neon accounts to organization accounts. Previously, this process required setting up a new organization, transferring projects, and entering billing details again. You can now convert your user account to an organization with a single action. This will instantly transfer all of your projects and billing to the new organization, with no service disruption and no changes to your connections. Your personal account will automatically switch to the Free Plan after conversion.

For more details on how to convert your account, see Convert your personal account.

And don't forget to check out this week's fixes and improvements:

Fixes & improvements
  • Neon Console enhancement

    We added a Settings option to the Account navigation sidebar in the Neon Console for easier access to personal and organization account settings. Account settings

  • Neon API changes

    • Updated the Create Project API to return a 404 error instead of a 500 error when an invalid region is specified.
    • Updated the project_id field for the Get consumption metrics for each project API. You can now specify project IDs as a comma-separated list in addition to an array of parameter values. This provides more flexibility when filtering responses by project. If omitted, the response will include all projects.
      • As an array: project_ids=cold-poetry-09157238&project_ids=quiet-snow-71788278
      • As a comma-separated list: project_ids=cold-poetry-09157238,quiet-snow-71788278
  • Fixes

    We fixed an issue with the Neon Vercel Integration where the PGPASSWORD variable in Vercel was not defined as expected after enabling branch protection on the main branch. Enabling branch protection resulted in a new password being generated for preview branches, rendering the existing PGPASSWORD setting invalid. To prevent this issue, a PGPASSWORD variable is now set for each new preview branch.

New monitoring graphs

We're continuing to improve visibility into your database performance with two new graphs on the Monitoring page: LFC hit rate and Working set size.

LFC graphs for monitoring page

working set graph for monitoring page

The Local file cache hit rate graph shows the percentage of read requests served from memory. A high hit rate indicates better performance, as more data is served from cache (faster) instead of being pulled from storage (slower). See What is the Local File Cache for more info.

The Working set size graph tracks the amount of data your database accesses over time. For best performance, your working set should fit within the LFC, minimizing slower queries that pull data from storage. See Working set size for details.

New banner for custom date range selection

Along with the new graphs on the Monitoring page, we also now added a banner to show your custom date range selection, making it a bit easier to keep track of your selected time frame when analyzing performance metrics.

custom date range selection banner on monitoring page

Postgres extension updates

We added support for the following extensions to Postgres 17.

ExtensionVersion
address_standardizer3.5.0
address_standardizer_data_us3.5.0
h34.1.3
h3_postgis4.1.3
pg_hashids1.2.1
pg_roaringbitmap0.5
pgjwt0.2.0
pgrouting3.6.2
plv83.5
postgis3.5.0
postgis_raster3.5.0
postgis_sfcgal3.5.0
postgis_tiger_geocoder3.5.0
postgis_topology3.5.0
prefix1.2.10
semver0.40.0
unit7

For a complete list of Postgres extensions supported by Neon, see Postgres extensions.

Support for removing backup branches created by restore operations

When working with branches, we recommend removing old and unused branches where possible. This helps free up disk space and keep your project organized. We’ve made that easier: you can now remove the backup branches created by restore operations on your project’s root branch (typically named main). Previously, the backup branches could not be removed.

For more details, and other recommendations, see Deleting backup branches.

Fixes & improvements
  • Added email verification for Microsoft login

    • New users signing in with Microsoft need to verify their email.
    • Existing users linking a Microsoft account will receive an email to complete the linking process.
  • Neon API change

    Removed the deprecated /consumption/projects endpoint entirely from the API.

  • Fixes

    • Fixed an issue where Free Plan users were sometimes unable to select a paid plan after their previous selection failed to register.
    • Fixed a problem with the Support form that became unresponsive when switching between Organizations.

10x-ing Projects on the Free Plan

10 projects on the Neon Free Plan

You may have seen the announcement already — Neon Free Plan users can now create up to 10 projects. We hope this increase will make it easier for you to learn a new stack, build the AI-powered app you've been thinking about, ship an MVP, upgrade to the next version of Postgres, or anything else the previous limit kept you from doing. Why did we make this change? Read all about it here: 10x-ing our Free Plan: Everyone Gets Ten Projects.

To create a new project, navigate to the Projects page in the Neon Console and click New Project.

Please note that Free Plan account-level allowances for compute hours, storage, and bandwidth remain unchanged.

Drag-to-zoom monitoring graphs

We've enhanced the graphs on our Monitoring page to support drag-to-zoom. You can now click and drag to zoom in on a selected range.

drag-to-zoom monitoring graphs

Fixes & improvements
  • Neon CLI update: We released a new version of the Neon CLI, with the following updates:

    • Fixed an issue with the login alias for the neon auth command.
    • Removed the previously deprecated set-primary primary subcommand from the branches command. It was replaced by the set-default subcommand.
    • Removed the previously deprecated --allow-list and --ip-primary-only options from the projects update command. Operations performed by these options are supported by the ip-allow command.
    • Removed the previously deprecated --primary-only option from the ip-allow command. It was replaced by the ip-allow add --protected-only option.
    • Updated the project list command to output a user-friendly message when there are no projects or shared projects to display.

    To update your Neon CLI installation to the latest version, follow our CLI upgrade instructions.

  • Create Support Ticket modal enhancements: We've made a few updates to the Create support ticket modal in the Neon Console:

    • Added a drop-down menu for selecting a personal account or organization.
    • To help resolve support cases faster, the consent option to allow Neon Support staff to connect to your database is now selected by default. You can leave this option selected or deselect it when opening a support ticket.
  • Organizations and Collaborators update: When a project collaborator is added as a member of an organization, they are now automatically removed as a collaborator from projects within that organization to avoid redundancy.

  • Neon Console enhancements: The table on the Projects page in the Neon Console now includes an Integrations column that lists your project's integrations. If there are no integrations, an Add option takes you to the Integrations page where you can view available integrations.

  • Extension update: Updated the neon extension to version 1.5 for all Postgres versions to add support for Neon-internal functions and views owned by the Neon system role.

  • Neon API change: The Delete a project endpoint now returns a 404 Not Found response instead of a 200 OK response if the project has already been deleted. This is a potentially breaking change for applications that expect a 200 OK response for all delete operations, regardless of whether a project was actually deleted.

  • Fixes:

    • Fixed an issue that prevented deleting a branch with an ephemeral compute endpoint created for performing a schema diff.
    • Fixed an issue where the GitHub integration drawer wouldn’t update after changes were made.
    • Fixed an issue in the GitHub integration that allowed connecting to the same GitHub repository from different Neon projects, which would overwrite previously configured variables.

Sign up for Neon Deploy

Join us online on October 30th at 10:00 AM PT to learn how Neon empowers developers to ship faster with Postgres. Tune in for Product updates and technical deep dives. Sign up today!

join us at Neon Deploy

Neon on Azure is open for beta

Neon on Azure is now available for public beta! Create a new project now and try it out.

azure project creation globe

More projects

Customers with database-per-tenant, developer platforms, and AI Agents told us they needed more projects: we've expanded the project limits across all paid Neon plans.

New limits:

  • Launch Plan: Up to 100 projects
  • Scale Plan: Up to 1,000 projects
  • Business Plan: Up to 5,000 projects

A reminder, last week we introduced the experimental @neondatabase/toolkit, which allows you to spin up a Postgres database in seconds and run SQL queries — ideal for quick setups and testing environments, and for taking advantage of your new, higher project limits.

ISO27110 & ISO27701 compliance

These new certifications add to our growing list of compliance achievements. For more about Neon's compliance milestones, see Compliance.

Database limits per branch

In case you missed last week's heads up — this week we've started enforcing a limit of 500 roles and 500 databases per branch. If you have any concerns about these new limits, please reach out to the Neon Support team. Previously, these limits were recommended but not enforced.

At a glance metrics for Free plan users

We're making it easier for Free Plan users to check how much room you've got left on your account-level metrics. Find it on your Projects page.

account metrics widget on all projects page

And we've also added a project-level usage widget on the Project Dashbaord as well, letting you know your current consumption levels for the month for each individual project.

project metrics on individual project page

Guests are now Collaborators

We've renamed Project sharing to Collaborators in both your Project and Organization settings pages in the Neon Console. This update streamlines collaboration with other users, whether from a personal account project or with external users for Organization-owned projects.

To manage collaboration from the project level, Project → Settings → Collaborators. And to manage collaboration for all projects in your Organization, Organization → People → Collaborators.

Fixes & improvements
  • We've removed deprecated language and actions from the Neon CLI. A few months ago, we started calling your root branch default instead of primary. The CLI now reflects this change: primary is no more, it's default everywhere. For more info, see set-default.
  • Added support for organization scopes in Neon OAuth, including create, read, update, delete, and manage organization permissions. See Neon OAuth integration for details.
  • Added an account selector to let users choose between personal and organization accounts when submitting a support ticket. This prevents issues for users with both free and paid accounts.
  • Fixed a UI issue where very long parent branch names broke the layout on the Branches view.
  • Resolved an issue where paid users incorrectly received alerts for hitting their monthly compute limits.
  • Corrected a display issue on the Monitoring page where charts showed an inaccurate pattern of breaks for autoscaling computes.

Support for Postgres 17

We're excited to announce that Neon now supports Postgres 17. To start using Postgres 17, create a new Neon project and select 17 as the Postgres version. For detailed instructions, refer to our Create a project guide.

Postgres 17 Create project

If you need to migrate data from an existing Neon project to one running Postgres 17, check out our Upgrading your Postgres version guide for supported migration options.

As always, it's important to thoroughly test before migrating production data or applications. We recommend reviewing the key changes in Postgres 17, which you can find in the Postgres Release 17 documentation.

Early Access to AI Features in Neon SQL Editor

Join our Early Access Program to try out the AI features we're testing in the Neon SQL Editor.

Explore three AI-driven features:

  • SQL generation: Convert natural language requests to SQL with ease. Press the ✨ button or use Cmd/Ctrl+Shift+M, type your request, and the AI assistant will generate the corresponding SQL. It’s schema-aware, so you can reference table names, functions, and other objects in your schema. SQL generation
  • Fix with AI: When your query returns an error, click Fix with AI next to the error message. The AI assistant will analyze the issue, suggest a fix, and update the SQL Editor so you can run the query again. Fix with AI
  • AI-generated query names: Queries in the Neon SQL Editor's History are automatically assigned descriptive names. This feature helps you quickly identify and reuse previous queries. AI-generated query names

A new Postgres toolkit for AI agents and test environments

We're excited to announce an experimental release of the @neondatabase/toolkit (@neon/toolkit on JSR). This toolkit lets you spin up a Postgres database in seconds and run SQL queries. It includes both the Neon API Client and the Neon Serverless Driver, making it an excellent choice for AI agents that need to quickly set up an SQL database, or for test environments where manually deploying a new database isn't practical.

With a few lines of code, you can create a Postgres database on Neon, run SQL queries, and tear down the database when you're done. Here's a quick look:

import { NeonToolkit } from "@neondatabase/toolkit";

const toolkit = new NeonToolkit(process.env.API_KEY!);
const project = await toolkit.createProject();

await toolkit.sql(
  project,
  `
    CREATE TABLE IF NOT EXISTS
        users (
            id UUID PRIMARY KEY,
            name VARCHAR(255) NOT NULL
        );
`,
);

await toolkit.sql(
  project,
  `
    INSERT INTO users (id, name) VALUES (gen_random_uuid(), 'Sam Altman');
`,
);

console.log(
  await toolkit.sql(
    project,
    `
    SELECT name FROM users;
`,
  ),
);

await toolkit.deleteProject(project);

As with all of our experimental features, changes are ongoing. If you have any feedback, we'd love to hear it. Let us know via the Feedback form in the Neon Console or our feedback channel on Discord.

Fixes & improvements
  • Released a new version of the Neon CLI with the following updates:

    • Fixed an issue where the neonctl -v command returned unknown instead of the CLI version.
    • Updated the neon projects create CLI command to support creating projects in the aws-ap-southeast-2 region, which was missing from the list of supported regions.
    • Added a warning to the neon branches create CLI command output for branches created from a protected parent branch. The warning notes that role passwords are changed. For more details, see New passwords generated for Postgres roles on child branches.

    To update your Neon CLI version, follow our CLI upgrade instructions.

  • The Drizzle Studio version that powers the Tables page in the Neon Console has been updated. For improvements and fixes in this version, see the Neon Drizzle Studio Integration Changelog.

  • We removed a restriction that prevented using the Schema Diff feature when IP Allow was enabled. Previously, Schema Diff couldn't compare branches protected by an IP Allow list.

  • Fixed an issue where timestamp values were displayed incorrectly on the Tables page. Timestamps were stored in UTC but shown in the user's local time zone.

  • Improved error messages on the Tables page after a Drizzle Studio connection failure.

  • The Refresh button on the Monitoring page now correctly refreshes any charts displaying an error.

  • Branch deletion operations triggered by a new preview deployment in the Neon Vercel Integration are now performed asynchronously, allowing preview deployment operations to proceed without delay.

  • Improved handling of long names for projects, branches, roles, and databases in the Neon Console.

  • Fixed an issue in the Neon Quickstart where the connection string would disappear and reappear.

  • Fixed an issue with storage usage values not updating correctly at the start of a new billing period after deleting all projects and downgrading.

Neon Organizations now in Public Beta

We're happy to announce that the Neon Organizations feature is now available in Public Beta.

get started with your new org

Create a new organization, transfer over your projects, invite your team members and get started collaborating. The Organizations feature lets you manage all of your team's projects under a single account — with billing, role management, and project transfer capabilities in one accessible location.

See Neon Organizations to get started. Organizations is a paid account feature.

Fixes & improvements
  • We added a Protect button to the default branch Overview page to make it easier to enable branch protection. The Protected Branches feature is available with the Neon Scale and Business plans. Protect button
  • The Created by column on the Branches page in the Neon Console now displays the creation source for branches created via GitHub or the Neon Vercel Integration. Hovering over the creation source will trigger a pop-up that provides links to an associated preview, repository, or code branch, where applicable. Branch created by column
  • Starting next week, we will start enforcing a limit of 500 roles and 500 databases per branch. If you have any concerns about these new limits, please reach out to the Neon Support team. Previously, these limits were recommended but not enforced.
  • We now support self-serve account deletion should you need to remove your Neon account for any reason. See Delete your account for details.

This week’s changelog – Live from Lisbon!

Neon Team Portugal

Our team is in Lisbon this week, wrapping up Q3 and refining our roadmap. It's been a great opportunity to reconnect, welcome new colleagues, meet with customers, and ensure we're delivering on the features and improvements our users are asking for.

As we look ahead as a team, here's a quick look back at some key features we've released over the past few months:

  • Inbound Logical Replication: Enables low-downtime migrations to Neon from other providers and between Neon projects. Check out our guides on Replicating Data to Neon and Project-to-Project Replication.
  • Organizations: Now available for Early Access users. This long-requested feature allows you to create and manage your organization's projects and teams from a single account. Join our Early Access Program and refer to the Organizations docs for more information.
  • Autoscaling GA: Neon's Autoscaling feature is now generally available, automatically adjusting resources as needed. Read the announcement here and explore the Autoscaling docs.
  • Autoscaling on Free Plan: Free Plan users can now experience Neon's Autoscaling. Learn more in the Autoscaling Guide.
  • A New Business Plan: Offers 500 GiB of storage and 1,000 compute hours, with potential cost savings for customers needing more storage than offered by our Scale plan. Learn more on our Pricing and Plans pages.

We do have a few small updates to share this week, which you can check out below.

Fixes & improvements
  • Resolved an issue in the Neon Console where a banner incorrectly indicated that the monthly storage limit was reached or nearly reached after a project had been deleted.
  • Improved the information provided on the Create new branch page and Reset branch modals.
  • For Early Access users, the Created by column on the Branches page in the Neon Console now displays the creation source for branches created via GitHub or the Neon Vercel Integration when BitBucket or GitHub is used as the source repository. Hovering over the creation source will trigger a pop-up that provides links to an associated preview, repository, or code branch, where applicable.
  • Improved the information about history retention provided on the SettingsStorage page in the Neon Console.
  • Improved how data is displayed in the Replication delay bytes and Replication delay seconds graphs on the Monitoring page in the Neon Console. The line segment was not displayed properly.
  • Feedback, Support, Docs, and Changelog links were moved from the Neon Console sidebar to a Help menu at the top of the console. Look for a "?" icon.
  • The number of reserved connections for the Neon-managed Postgres superuser account was increased from 4 to 7.
  • The Time Travel toggle in the Neon SQL Editor is now accessible via a new icon above the editor window.

A new Business plan with more compute and storage

New Business Plan

We're pleased to announce that we've launched a new Business plan that provides higher storage and compute allowances (500 GiB of storage and 1,000 compute hours) in addition to all of Neon's advanced features. This plan offers potential cost savings for customers requiring more than our Scale plan provides.

To learn more about our new plan, please refer to our Pricing page and Plans documentation.

New monitoring graphs for Read Replicas

We added two new charts to the Monitoring page in the Neon Console for monitoring Read Replica replication lag. These charts are visible when selecting a Replica compute from the Compute drop-down menu.

  • Replication delay bytes: Measures the total size, in bytes, of the data that has been sent from the primary compute but has not yet been applied on the replica.

    Replication delay bytes

  • Replication delay seconds: Indicates the time delay, in seconds, between the last transaction committed on the primary compute and the application of that transaction on the replica.

    Replication delay seconds

For more information, see Monitoring dashboard.

A Protected Branches update

New passwords are automatically generated for Postgres roles on branches created from protected branches. You can learn more about this feature here.

Previously, resetting or restoring a child branch (where passwords were previously regenerated) reset the passwords back to those used on the parent branch. Now, when you perform a branch reset or restore operation from a protected branch, the role passwords on the child branch are preserved.

The protected branches feature is available with the Neon Scale or Business plan. To learn more, refer to our Protected Branches guide.

Fixes & improvements
  • The Branches page now includes a Created by column that displays the name and avatar of the user who created the branch, if available. Additionally, a Web identifier tag is displayed if the branch was created via the Neon Console.
  • Fixed an issue on the Billing page where an incorrect branch limit was displayed for a project shared by a paid Neon account.
  • Fixed an issue that prevented restoring a protected branch.
  • Fixed an issue with the Neon Vercel Integration that caused a Something went wrong error when creating a new Neon project during integration installation.
  • Fixed an issue with the database selector in the Neon SQL Editor. Selecting a different database did not change the database.

Autoscaling is now GA

visualization for autoscaling

In case you missed the announcement earlier this week, we're excited to share that Neon's Autoscaling feature is now generally available. Autoscaling has been a core objective for Neon from the very beginning. With Autoscaling, your database automatically adjusts its compute resources up or down based on demand, including scaling down to zero when not in use. This feature is now ready for production, making it easier than ever to manage workloads efficiently.

If you're not yet familiar with Neon's Autoscaling feature, you can learn more here:

Autoscaling on the Free Plan

In addition to our Autoscaling GA announcement, we've made Autoscaling available on our Free Plan, where you can automatically scale computes from 0.25 vCPU with 1 GB of RAM up to 2 vCPU with 8 GB of RAM. To learn how, see Enabling Autoscaling.

When you try Autoscaling on the Free Plan, we recommend monitoring your monthly compute hour allowance. A compute that scales up regularly to meet demand will consume your compute hour allowance more quickly.

Postgres version updates

Supported Postgres versions were updated to 14.13, 15.8, and 16.4, respectively.

Upcoming change for branch reset and restore from a protected branch

A few weeks ago, we introduced a new protected branches feature: When you create a child branch from a protected branch, new passwords are automatically generated for the matching Postgres roles on the child branch. This helps prevent the exposure of passwords that could be used to access your protected branch. You can read more about this feature here.

Next week, we'll be making a related change, and we wanted to give you a heads-up in case any updates are needed for your CI scripts or workflows. Coming next week: When you perform a branch reset or restore operation on a child branch, the role passwords on the child branch will be preserved. Currently, resetting or restoring a child branch (where passwords were previously regenerated) resets the passwords back to those used on the parent branch.

The protected branches feature is available with the Neon Scale plan. To learn more, refer to our Protected Branches guide.

Fixes & improvements
  • The Reset a Neon branch GitHub Action, which resets a child branch with the latest data from its parent, now outputs connection string values. New outputs include:
    • branch_id: The ID of the newly reset branch.
    • db_url: The database connection string for the branch after the reset.
    • db_url_with_pooler: The pooled database connection string for the branch after the reset.
    • host: The branch host after the reset.
    • host_with_pooler: The branch host with the connection pooling option after the reset.
    • password: The Postgres role password for connecting to the branch database after the reset.
  • We've revamped the Usage widget on the Project Dashboard for Free Plan users, making it easier to monitor your usage allowances. Now prominently positioned at the top of the dashboard, the Usage widget provides an at-a-glance view of your monthly totals for Storage, Compute, Branch compute, and Branches. For an overview of Neon Free Plan allowances, please see Free Plan.
  • Fixed an issue with the Neon CLI's neonctl -v command. The command returned unknown instead of the CLI version number. Thanks to community member @mrl5 for the contribution.
  • Fixed an issue with the Neon Docs site navigation. Thanks to community member @lemorage for the contribution.

Replicating data from Neon for Change Data Capture (CDC) is now GA

Neon logical replication banner

Neon is pleased to announce GA support for replicating data from Neon to other data services and platforms for Change Data Capture (CDC). Define Neon as a publisher to stream data to a variety of external destinations, including data warehouses, analytical database services, messaging platforms, event-streaming platforms, and external Postgres databases. This feature is open to all Neon users. To get started, jump into one of our step-by-step logical replication guides.

Replicating data to Neon is now available in Beta

Migrate data to Neon from other Postgres providers by defining Neon as a logical replication subscriber. This feature supports near-zero downtime data migrations, continuous replication setups, and migrating data between Neon projects. Refer to our logical replication migration guides to get started.

As with all of our Beta features, improvements are ongoing. If you have any feedback, we'd love to hear it. Let us know via the Feedback form in the Neon Console or our feedback channel on Discord.

Early Access to Neon Organizations

We're also very happy to announce that Neon Organizations are now available for members of our Early Access Program.

get started with your new org

Create a new organization, transfer over your projects, invite your team and get started collaborating. Join now to get a first look at Neon Organizations and other upcoming features before they go live.

See Neon Organizations to learn more.

Console enhancements

We've made several enhancements to the Neon Console to improve your experience and streamline your interaction with our user interface.

  • You can now access Neon projects shared with you from the project breadcrumb selector in the Neon Console. Project breadcrumb selector
  • The Billing page for Free Plan users now shows a percentage value for branch compute usage. Compute branches metric
  • We've added a new example to the Neon Console Quickstart showing how to connect to to your Neon database from NestJS. You can access the Quickstart from your Project Dashboard. NestJS example
  • The Primary compute column on the Branches page now shows your configured autoscaling range, replacing the Autoscales badge that was shown previously. Autoscaling range
Fixes & improvements
  • Fixed an issue that prevented database and role names from being fully displayed in the SettingsDefault database and role section on the Vercel integration drawer, accessed from the Integrations page in the Neon Console.
  • Queries saved to the Neon SQL Editor Saved list are now limited to 9 KB in length. A similar restriction was introduced for the Neon SQL Editor History list last week. While you can execute longer queries from the Neon SQL Editor, any query exceeding 9 KB will be truncated when saved. A -- QUERY TRUNCATED comment is added at the beginning of these queries to indicate truncation.
  • We updated the Drizzle Studio version that powers the Tables page in the Neon Console. This update addresses an issue where updating a column value in one row via the table editor updated the same column value in other rows.
  • Fixed an issue in the Neon Console where page labels in the sidebar were not highlighted when selected.
  • Fixed an issue that caused a Something went wrong error to appear briefly after deleting a project from the Settings page in the Neon Console.
  • Removed information about the Free Plan that was displayed when creating a project with a paid plan account.
  • Fixed an issue on the Projects page where a deleted project was only removed from the projects list after a page refresh.
  • Fixed an issue with the Time Travel Assist feature on the Restore page in the Neon Console. Attempting to run a time travel query resulted in a Something went wrong error.
  • Fixed a Neon CLI issue that caused the neon create-app command to fail when providing an app name.
Was this page helpful?