Repository navigation
Include curated monthly highlights in releases overview - #1546
Merged
Merged
Conversation
Contributor
Validate docs site✓ INFO: A live preview of the docs site is available — Open the preview |
Contributor
Lighthouse check results✓ INFO: Average accessibility score is 0.91 (required: ≥0.9) — View the workflow run Audit mode: changed pages (1 URL(s)) Show Lighthouse scoresCommit SHA: 028cdd6 For a thorough audit, run the Lighthouse check workflow manually (Actions → Lighthouse check → Run workflow) with depth 0–2, or add the
|
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
1 participant
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 and why?
The release overview's latest highlights table only scans legacy per-PR pages, so it omits the eight curated 26.10 highlights even though the monthly notes are deployed. Include published monthly highlight metadata in the same table; titles link to their sections in the monthly release notes. The existing six-row limit and historical entries remain.
How to test
Rendered
all-releases.qmd,feature-highlights.qmd, and the 26.10 notes locally with release sources from the companion PR. Confirmed the overview shows 26.10 dated October 2, 2026, the latest table displays six current highlights, and the full highlights page lists all eight. Clicked the announcements title in a browser and verified its destination section. Every generated highlight fragment resolves. Local renders warned about library API sources absent from this checkout; these are populated in the hosted build.Dependencies, breaking changes, and deployment notes
Depends on release-notes #175, which updates the current-train metadata and supplies the eight highlight entries and stable anchors. Merge that companion first so the documentation build can fetch it from release-notes main. Staging rebuilds after merge; production promotion remains a separate step.
Release notes
Internal release-index maintenance.
Checklist