Skip to content

docs: add recent minor version rollout timeline to Postgres version policy page #5603

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bgrenon wants to merge 3 commits into
base: main
Choose a base branch
from
Open

docs: add recent minor version rollout timeline to Postgres version policy page #5603

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
452bf22
docs: add Postgres minor version rollout timeline
Aug 21, 2026
d103ec2
docs: qualify rollout-speed and automation claims on minor version ti…
Aug 21, 2026
e9e67f2
docs: add recent minor version rollout timeline to Postgres version p…
Aug 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion content/docs/postgresql/postgres-version-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ summary: >-
Minor release downgrades and version skipping are not supported. Upgrading
to a new major version requires creating a new project and migrating data.
enableTableOfContents: true
updatedOn: '2026-07-31T15:27:48.506Z'
updatedOn: '2026-08-21T15:27:30.599Z'
---

This topic outlines [Neon's Postgres Version Support Policy](#neon-version-support-policy).
Expand Down Expand Up @@ -63,6 +63,21 @@ Neon only supports the latest minor release for each major Postgres version. For

Neon does not support skipping minor releases or downgrading to a previous minor release.

#### Recent minor version rollouts

@danieltprice danieltprice Aug 24, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might need to take a look at first available dates.

The table below shows when recent Postgres releases become available on Neon. The three most recent on-schedule community releases each reached Neon within five days of the announcement.

@dcw-data dcw-data Aug 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure we want the second sentence...doesn't add much value. If we want to say something beyond the table perhaps "Neon aims to make new minors available within one week of community release."

Suggested change
The table below shows when recent Postgres releases become available on Neon. The three most recent on-schedule community releases each reached Neon within five days of the announcement.
The table below shows when recent Postgres releases become available on Neon.


| Postgres release date | Versions in the release | First available on Neon | Time to availability |
| --------------------- | -------------------------------- | ----------------------- | -------------------- |
| 2026-08-13 | 18.6, 17.11, 16.15, 15.19, 14.24 | 2026-08-18 | 5 days |
| 2026-05-14 | 18.4, 17.10, 16.14, 15.18, 14.23 | 2026-05-19 | 5 days |
| 2026-02-12 | 18.2, 17.8, 16.12, 15.16, 14.21 | 2026-02-14 | 2 days |
| 2025-11-13 | 18.1, 17.7, 16.11, 15.15, 14.20 | 2025-12-04 | 21 days |

The **First available on Neon** date marks when a release first became available to run, not the point at which every compute is running it; each compute picks it up on the next restart, as described above.

As of August 2026, Neon runs the latest community minor release for every supported major version: 18.6, 17.11, 16.15, 15.19, and 14.24. For the current version list, see [Compatibility](/docs/reference/compatibility).

#### Manual actions after minor release upgrades

As a managed service, Neon strives to manage all minor version updates automatically, minimizing the need for user intervention. However, certain updates, such as security fixes, may require decisions that depend on your application and cannot be fully automated.
Expand Down
Loading