-
Notifications
You must be signed in to change notification settings - Fork 311
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.
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
Merged
+16
−1
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
452bf22
docs: add Postgres minor version rollout timeline
d103ec2
docs: qualify rollout-speed and automation claims on minor version ti…
e9e67f2
docs: add recent minor version rollout timeline to Postgres version p…
b499ca1
docs: update rollout dates to verified values and trim opener
03e70bb
Update content/docs/postgresql/postgres-version-policy.md
bgrenon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -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). | ||||||
|
|
@@ -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 | ||||||
|
|
||||||
| 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. | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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
|
||||||
|
|
||||||
| | 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. | ||||||
|
|
||||||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-checked the dates in Grafana - confirmed, with small changes in the last commit.