Skip to content

fix: keep release badges current after docs sync - #257

Merged
hannesrudolph merged 1 commit into
mainfrom
fix/current-release-announcement
Oct 3, 2026
Merged

hannesrudolph merged 1 commit into
mainfrom
fix/current-release-announcement

Conversation

@hannesrudolph

Copy link
Copy Markdown
Member

What Problem This Solves

Fixes the Releases badge and homepage announcement staying on v2026.9.7 after newer release notes are published.

User Impact

Readers see the newest available stable release and follow its correct release-notes link, including v2026.9.8.

Why This Change Was Made

The badge now follows the synced English release pages instead of a manually pinned version. It uses the selected page's summary and excludes hidden, draft, unreleased and beta pages. Existing localized labels and links are preserved.

Evidence

  • All five focused announcement tests pass, including a full build that advances the badge after a newer release page is added.
  • Coverage includes numeric version ordering, hidden/draft/beta exclusion, translated links, and behavior after navigation and reload.
  • A bounded 30-page preview renders v2026.9.8 in the sidebar and homepage announcement; the sidebar badge was visually checked.
  • Independent code review passed. No generated docs, translations, or release-note copy were edited.

@hannesrudolph
hannesrudolph requested a review from a team as a code owner October 3, 2026 04:28
@hannesrudolph
hannesrudolph merged commit 35695bc into main Oct 3, 2026
5 checks passed
@hannesrudolph
hannesrudolph deleted the fix/current-release-announcement branch October 3, 2026 04:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant