From 452bf22646ebb9ba9f677ce569c12d66dfd7407d Mon Sep 17 00:00:00 2001 From: Barry Grenon Date: Fri, 21 Aug 2026 12:38:49 +0000 Subject: [PATCH 1/5] docs: add Postgres minor version rollout timeline Adds a customer-facing page recording how quickly recent PostgreSQL community minor releases became available on Neon computes, plus a nav entry under Products > Postgres between "Version support" and "Upgrade". The page is the evidence behind the fast-minor-adoption promise in the version support policy; it links to the policy rather than restating it. Co-authored-by: Isaac --- content/docs/navigation.yaml | 3 ++ .../postgres-minor-version-timeline.md | 48 +++++++++++++++++++ 2 files changed, 51 insertions(+) create mode 100644 content/docs/postgresql/postgres-minor-version-timeline.md diff --git a/content/docs/navigation.yaml b/content/docs/navigation.yaml index b64220e096e..6ee4928bd0a 100644 --- a/content/docs/navigation.yaml +++ b/content/docs/navigation.yaml @@ -521,6 +521,9 @@ - title: Version support slug: postgresql/postgres-version-policy icon: version + - title: Minor version timeline + slug: postgresql/postgres-minor-version-timeline + icon: changelog - title: Upgrade slug: postgresql/postgres-upgrade icon: upgrade diff --git a/content/docs/postgresql/postgres-minor-version-timeline.md b/content/docs/postgresql/postgres-minor-version-timeline.md new file mode 100644 index 00000000000..de3cf5262a2 --- /dev/null +++ b/content/docs/postgresql/postgres-minor-version-timeline.md @@ -0,0 +1,48 @@ +--- +title: Postgres minor version rollout timeline +summary: >- + A record of how quickly recent PostgreSQL community minor releases became + available on Neon computes. Postgres 18 was available on the day it went GA, + and the three most recent on-schedule minor batches reached computes within + five days of the community announcement. +enableTableOfContents: true +--- + +The PostgreSQL Global Development Group ships a minor release for every supported major version at least once a quarter, plus out-of-cycle releases when a security fix is too urgent to wait. Neon rebuilds its compute images from each of those releases and rolls them out automatically: you don't request the update, and you don't schedule a maintenance window. + +The [Postgres version support policy](/docs/postgresql/postgres-version-policy) describes that commitment. This page is the record of how it has played out. For recent on-schedule community releases, the new minor versions have reached Neon computes within a week of the community announcement, and Postgres 18 was available the day it went GA. + +## Rollout timeline + +The table covers community releases from the Postgres 18 GA onward, newest first. + +| PostgreSQL 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 | +| 2025-09-25 | 18.0 (new major version) | 2025-09-24 | At release | + +Notes on individual rows: + +- **Postgres 18 GA:** Neon builds its compute images from the community release wrap, which is tagged a few days ahead of the announcement. Postgres 18 computes were therefore ready to run as the GA announcement went out on 2025-09-25. +- **November 2025:** Neon moved to this batch about two weeks after the announcement, a longer cycle than the batches above it. +- **August 2025:** Neon did not ship the August 2025 community batch (17.6, 16.10, 15.14, 14.19) as a standalone update. Those fixes reached computes in late November 2025, days before the November 2025 batch superseded them. +- **Earlier 2025 releases:** Neon does not have complete rollout records for community releases before September 2025, so they are not listed here. + +Each update is announced in the [Neon Changelog](/docs/changelog). + +## How these dates map to your computes + +The **First available on Neon** date is the point at which a release became available to run. It marks the start of the rollout, not the moment every compute is running the new version. + +Each compute picks up a new minor version the next time it restarts, for any reason, so computes move onto it across the following days. If your compute suspends when idle, it is updated the next time it wakes. If your compute is always active and you want to pick up an update right away, see [Restart a compute](/docs/manage/computes#restart-a-compute). + +Minor releases and security patches require no action from you. In the rare case where an update does need a decision that depends on your application, Neon notifies you directly; see [Manual actions after minor release upgrades](/docs/postgresql/postgres-version-policy#manual-actions-after-minor-release-upgrades). + +## Current minor versions + +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). + + From d103ec2d3a3f662cdd85d1ae7db5c3ecab264668 Mon Sep 17 00:00:00 2001 From: Barry Grenon Date: Fri, 21 Aug 2026 12:46:10 +0000 Subject: [PATCH 2/5] docs: qualify rollout-speed and automation claims on minor version timeline Addresses cross-vendor review of #5603: - Scope the speed claim to the three most recent on-schedule batches (within five days), matching the summary frontmatter, and point at the notes for the exceptions. The previous wording claimed "recent on-schedule releases" landed within a week, which the November 2025 row (21 days) contradicts. - Stop asserting that every community release is independently rebuilt and rolled out, which the August 2025 batch contradicts. The no-request / no-maintenance-window point is unchanged. - "typically require no action from you", since the next sentence covers the rare application-dependent case. Co-authored-by: Isaac --- content/docs/postgresql/postgres-minor-version-timeline.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/docs/postgresql/postgres-minor-version-timeline.md b/content/docs/postgresql/postgres-minor-version-timeline.md index de3cf5262a2..85280bf1d7a 100644 --- a/content/docs/postgresql/postgres-minor-version-timeline.md +++ b/content/docs/postgresql/postgres-minor-version-timeline.md @@ -8,9 +8,9 @@ summary: >- enableTableOfContents: true --- -The PostgreSQL Global Development Group ships a minor release for every supported major version at least once a quarter, plus out-of-cycle releases when a security fix is too urgent to wait. Neon rebuilds its compute images from each of those releases and rolls them out automatically: you don't request the update, and you don't schedule a maintenance window. +The PostgreSQL Global Development Group ships a minor release for every supported major version at least once a quarter, plus out-of-cycle releases when a security fix is too urgent to wait. Neon builds updated compute images from community releases and rolls them out automatically: you don't request the update, and you don't schedule a maintenance window. -The [Postgres version support policy](/docs/postgresql/postgres-version-policy) describes that commitment. This page is the record of how it has played out. For recent on-schedule community releases, the new minor versions have reached Neon computes within a week of the community announcement, and Postgres 18 was available the day it went GA. +The [Postgres version support policy](/docs/postgresql/postgres-version-policy) describes that commitment. This page is the record of how it has played out. The three most recent on-schedule community releases each reached Neon computes within five days of the announcement, and Postgres 18 was available the day it went GA. Adoption has not always been that quick; the notes under the table explain the exceptions. ## Rollout timeline @@ -39,7 +39,7 @@ The **First available on Neon** date is the point at which a release became avai Each compute picks up a new minor version the next time it restarts, for any reason, so computes move onto it across the following days. If your compute suspends when idle, it is updated the next time it wakes. If your compute is always active and you want to pick up an update right away, see [Restart a compute](/docs/manage/computes#restart-a-compute). -Minor releases and security patches require no action from you. In the rare case where an update does need a decision that depends on your application, Neon notifies you directly; see [Manual actions after minor release upgrades](/docs/postgresql/postgres-version-policy#manual-actions-after-minor-release-upgrades). +Minor releases and security patches typically require no action from you. In the rare case where an update does need a decision that depends on your application, Neon notifies you directly; see [Manual actions after minor release upgrades](/docs/postgresql/postgres-version-policy#manual-actions-after-minor-release-upgrades). ## Current minor versions From e9e67f26ae44ec4186e2fc37b3e80f1492a5a4ff Mon Sep 17 00:00:00 2001 From: Barry Grenon Date: Fri, 21 Aug 2026 15:27:30 +0000 Subject: [PATCH 3/5] docs: add recent minor version rollout timeline to Postgres version policy page Adds a "Recent minor version rollouts" subsection to the existing Postgres version support policy page, inside "Minor releases". It records when recent community minor releases became available on Neon, as the evidence behind the section's existing claim that new minors land at or near the official release date. This replaces the earlier standalone-page design: the standalone postgres-minor-version-timeline.md page and its navigation.yaml entry are removed, so navigation.yaml is back to its original state and the timeline lives on the policy page instead. Co-authored-by: Isaac --- content/docs/navigation.yaml | 3 -- .../postgres-minor-version-timeline.md | 48 ------------------- .../postgresql/postgres-version-policy.md | 17 ++++++- 3 files changed, 16 insertions(+), 52 deletions(-) delete mode 100644 content/docs/postgresql/postgres-minor-version-timeline.md diff --git a/content/docs/navigation.yaml b/content/docs/navigation.yaml index 6ee4928bd0a..b64220e096e 100644 --- a/content/docs/navigation.yaml +++ b/content/docs/navigation.yaml @@ -521,9 +521,6 @@ - title: Version support slug: postgresql/postgres-version-policy icon: version - - title: Minor version timeline - slug: postgresql/postgres-minor-version-timeline - icon: changelog - title: Upgrade slug: postgresql/postgres-upgrade icon: upgrade diff --git a/content/docs/postgresql/postgres-minor-version-timeline.md b/content/docs/postgresql/postgres-minor-version-timeline.md deleted file mode 100644 index 85280bf1d7a..00000000000 --- a/content/docs/postgresql/postgres-minor-version-timeline.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Postgres minor version rollout timeline -summary: >- - A record of how quickly recent PostgreSQL community minor releases became - available on Neon computes. Postgres 18 was available on the day it went GA, - and the three most recent on-schedule minor batches reached computes within - five days of the community announcement. -enableTableOfContents: true ---- - -The PostgreSQL Global Development Group ships a minor release for every supported major version at least once a quarter, plus out-of-cycle releases when a security fix is too urgent to wait. Neon builds updated compute images from community releases and rolls them out automatically: you don't request the update, and you don't schedule a maintenance window. - -The [Postgres version support policy](/docs/postgresql/postgres-version-policy) describes that commitment. This page is the record of how it has played out. The three most recent on-schedule community releases each reached Neon computes within five days of the announcement, and Postgres 18 was available the day it went GA. Adoption has not always been that quick; the notes under the table explain the exceptions. - -## Rollout timeline - -The table covers community releases from the Postgres 18 GA onward, newest first. - -| PostgreSQL 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 | -| 2025-09-25 | 18.0 (new major version) | 2025-09-24 | At release | - -Notes on individual rows: - -- **Postgres 18 GA:** Neon builds its compute images from the community release wrap, which is tagged a few days ahead of the announcement. Postgres 18 computes were therefore ready to run as the GA announcement went out on 2025-09-25. -- **November 2025:** Neon moved to this batch about two weeks after the announcement, a longer cycle than the batches above it. -- **August 2025:** Neon did not ship the August 2025 community batch (17.6, 16.10, 15.14, 14.19) as a standalone update. Those fixes reached computes in late November 2025, days before the November 2025 batch superseded them. -- **Earlier 2025 releases:** Neon does not have complete rollout records for community releases before September 2025, so they are not listed here. - -Each update is announced in the [Neon Changelog](/docs/changelog). - -## How these dates map to your computes - -The **First available on Neon** date is the point at which a release became available to run. It marks the start of the rollout, not the moment every compute is running the new version. - -Each compute picks up a new minor version the next time it restarts, for any reason, so computes move onto it across the following days. If your compute suspends when idle, it is updated the next time it wakes. If your compute is always active and you want to pick up an update right away, see [Restart a compute](/docs/manage/computes#restart-a-compute). - -Minor releases and security patches typically require no action from you. In the rare case where an update does need a decision that depends on your application, Neon notifies you directly; see [Manual actions after minor release upgrades](/docs/postgresql/postgres-version-policy#manual-actions-after-minor-release-upgrades). - -## Current minor versions - -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). - - diff --git a/content/docs/postgresql/postgres-version-policy.md b/content/docs/postgresql/postgres-version-policy.md index 90883463e84..dcdc670eb22 100644 --- a/content/docs/postgresql/postgres-version-policy.md +++ b/content/docs/postgresql/postgres-version-policy.md @@ -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. + +| 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. From b499ca1eb7c0da6c8fdd8c016606485d80eb59f2 Mon Sep 17 00:00:00 2001 From: Barry Grenon Date: Wed, 26 Aug 2026 14:40:58 +0000 Subject: [PATCH 4/5] docs: update rollout dates to verified values and trim opener Co-authored-by: Isaac --- content/docs/postgresql/postgres-version-policy.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/docs/postgresql/postgres-version-policy.md b/content/docs/postgresql/postgres-version-policy.md index dcdc670eb22..2f460472b97 100644 --- a/content/docs/postgresql/postgres-version-policy.md +++ b/content/docs/postgresql/postgres-version-policy.md @@ -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-08-21T15:27:30.599Z' +updatedOn: '2026-08-26T14:40:58.742Z' --- This topic outlines [Neon's Postgres Version Support Policy](#neon-version-support-policy). @@ -65,14 +65,14 @@ Neon does not support skipping minor releases or downgrading to a previous minor #### 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. +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 | +| 2026-02-12 | 18.2, 17.8, 16.12, 15.16, 14.21 | 2026-02-13 | 1 day | +| 2025-11-13 | 18.1, 17.7, 16.11, 15.15, 14.20 | 2025-12-03 | 20 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. From 03e70bb279a2d0918a2fdbbbd5f3909d4ca630b2 Mon Sep 17 00:00:00 2001 From: Barry Grenon Date: Wed, 26 Aug 2026 17:02:47 -0300 Subject: [PATCH 5/5] Update content/docs/postgresql/postgres-version-policy.md Co-authored-by: Daniel <10074684+danieltprice@users.noreply.github.com> --- content/docs/postgresql/postgres-version-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/postgresql/postgres-version-policy.md b/content/docs/postgresql/postgres-version-policy.md index 2f460472b97..7cc98aa127a 100644 --- a/content/docs/postgresql/postgres-version-policy.md +++ b/content/docs/postgresql/postgres-version-policy.md @@ -65,7 +65,7 @@ Neon does not support skipping minor releases or downgrading to a previous minor #### Recent minor version rollouts -The table below shows when recent Postgres releases become available on Neon. +The table below shows when recent Postgres releases became available on Neon. | Postgres release date | Versions in the release | First available on Neon | Time to availability | | --------------------- | -------------------------------- | ----------------------- | -------------------- |