Skip to content

Give each version of the unified release notes preview its own page - #4486

Merged
Mpdreamz merged 2 commits into
mainfrom
fix/unified-release-notes-nav-areas
Oct 16, 2026
Merged

Mpdreamz merged 2 commits into
mainfrom
fix/unified-release-notes-nav-areas

Conversation

@Mpdreamz

Copy link
Copy Markdown
Member

The unified release notes preview now has a page for each version of a product, for example /release-notes/kibana/9.6.0, so a version can be shared by its URL. Every page warns that the version is unreleased, the entries are grouped by area, and the navigation shows product and version names.

Affects: Release notes

Prompt summary: Get the unified release notes preview ready to share with writers. The first publish shows every version on one page with a navigation that reads "Release notes" four times, no areas, and no hint that the versions are unreleased.

Why

The generated site renders all versions of a product on one page, so there is no URL for a single version. The navigation labels each product page "Release notes", which hides which product a page belongs to. The pages do not group entries by area as the published release notes do, and nothing tells a reader that the versions have not shipped.

What

A page per version

UnifiedReleaseNotesDocset.Generate takes the versions of each product, read from the loaded bundles and ordered newest first. It writes release-notes/<product>/<version>.md with the changelog directive and :version:. The product page lists the versions and links to them. Known issues, breaking changes and deprecations stay one page per product, across versions.

Areas and names

The version pages set :subsections:, so Features and Fixes group by area. The product page is named after the product in the navigation, and a version page after the version.

Unreleased notice

Every generated page opens with a warning admonition that this is a preview of an unreleased version.

Verify

dotnet test tests/Elastic.Documentation.Build.Tests/ --treenode-filter "/*/*/UnifiedReleaseNotesTests/*"
dotnet run --project src/tooling/docs-builder -- release unified build preview --bundles-dir <bundles> --output /tmp/site

Open /tmp/site/release-notes/kibana/9.6.0/index.html: the warning is at the top, the sidebar lists the versions, and area names appear in bold above their entries.

Out of scope: Which versions the site shows is decided by the workflow in docs-internal-workflows, which will bundle only preview targets.

🤖 Generated with Claude Code

The generated docset has a page per product and version, named after the version, so a version can be shared by its URL. The product page lists the versions, the pages group entries by area, the navigation names the product and the version instead of "Release notes", and every page warns that the version is unreleased.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@Mpdreamz
Mpdreamz requested a review from a team as a code owner October 16, 2026 09:29
@Mpdreamz
Mpdreamz requested a review from akira28 October 16, 2026 09:29
Comment thread tests/Elastic.Documentation.Build.Tests/UnifiedReleaseNotesTests.cs
@github-actions

Copy link
Copy Markdown
Contributor

Docs preview (local build)

Handbook preview: https://docs-v3-preview.elastic.dev/elastic/docs-builder/pull/4486/

A bundle targeting a release tag like v9.5.0 generates a version page
filtered by :version: 9.5.0, but ChangelogVersionMatch compared the
bundle's target and file name without stripping 'v' from either side.
With a product-prefixed bundle file name, neither side matched, so the
version page silently omitted all of its release notes and warned.

Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@Mpdreamz
Mpdreamz merged commit f56966e into main Oct 16, 2026
32 checks passed
@Mpdreamz
Mpdreamz deleted the fix/unified-release-notes-nav-areas branch October 16, 2026 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants