docs: add recent minor version rollout timeline to Postgres version policy page - #5603
Open
bgrenon wants to merge 3 commits into
Open
docs: add recent minor version rollout timeline to Postgres version policy page#5603bgrenon wants to merge 3 commits into
bgrenon wants to merge 3 commits into
Conversation
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 <no-reply@databricks.com>
bgrenon
requested review from
andrelandgraf,
danieltprice,
philip and
ruf-io
as code owners
August 21, 2026 12:40
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
bgrenon
marked this pull request as draft
August 21, 2026 12:44
…meline 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 <no-reply@databricks.com>
…olicy 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 <no-reply@databricks.com>
bgrenon
changed the title
bgrenon
marked this pull request as ready for review
August 21, 2026 15:43
dcw-data
reviewed
Aug 21, 2026
|
|
||
| #### 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.
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. |
dcw-data
approved these changes
Aug 21, 2026
dcw-data
left a comment
dcw-data
left a comment
There was a problem hiding this comment.
Minor suggestion but no need to block on me.
| Neon does not support skipping minor releases or downgrading to a previous minor release. | ||
|
|
||
| #### Recent minor version rollouts | ||
|
|
Collaborator
There was a problem hiding this comment.
We might need to take a look at first available dates.
danieltprice
requested changes
Aug 24, 2026
danieltprice
left a comment
danieltprice
left a comment
Collaborator
There was a problem hiding this comment.
Let's take a look at first available dates before publishing.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What
Adds a Recent minor version rollouts subsection to the Postgres version support policy page, under Minor releases.
That section already notes new minor versions are usually available within a few days of the official Postgres release date. This adds a short, dated table showing when recent community minor releases became available on Neon.
Changes
content/docs/postgresql/postgres-version-policy.md— adds the subsection (a four-row table and two clarifying sentences).