Skip to content

docs: derive release-notes nav from the release-notes directory - #1732

Merged
mohnjiles merged 1 commit into
mainfrom
docs/derive-release-notes-nav
Aug 30, 2026
Merged

docs: derive release-notes nav from the release-notes directory#1732
mohnjiles merged 1 commit into
mainfrom
docs/derive-release-notes-nav

Conversation

@mohnjiles

Copy link
Copy Markdown
Member

Summary

Follow-up to #1730: the 2.16.3 technical notes page deployed fine but was unreachable — the site nav's Release Notes link and the sidebar's page list both hardcoded 2.16.2.

Rather than bump two hardcoded strings per release (the drift that just bit us), both now derive from the files in docs/release-notes/ at build time, newest first. Adding a release's markdown page is the whole job; the nav can't lag again.

  • Nav Release Notes entry → newest version in the directory
  • Sidebar → all versions, descending
  • Filename filter is strict (N.N.N.md) so stray files can't leak into nav

This also makes the release-checklist step suggested in #1730 unnecessary for the nav specifically — the remaining checklist item is just "write the page."

🤖 Generated with Claude Code

The nav link and sidebar list hardcoded 2.16.2, so the freshly-published
2.16.3 page was live but unreachable from the site nav. Both now derive
from the files in docs/release-notes/ (newest first) — adding a release's
page is the whole job.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@mohnjiles
mohnjiles enabled auto-merge August 30, 2026 22:41
@mohnjiles
mohnjiles merged commit e4297ca into main Aug 30, 2026
5 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Aug 30, 2026
@mohnjiles
mohnjiles deleted the docs/derive-release-notes-nav branch August 30, 2026 22:44
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants