docs: add redirects for hotfix release notes URLs#17630
Merged
lakshay-nasa merged 3 commits intoJun 4, 2026
Merged
Conversation
github-actions
Bot
added
the
community-contribution
maggiehays
added
the
needs-review
javabrett
reviewed
Jun 2, 2026
maggiehays
added
merge-pending-ci
javabrett
approved these changes
Jun 4, 2026
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.
Summary
Hotfix release notes (e.g., v1.0.2, v0.3.17.3) are appended as sections within their base release page (e.g.,
/v_1_0_0/#v102), not as standalone pages. URLs like/v_1_0_2/return 404.Adds a lightweight postBuild plugin that creates meta-refresh redirects for all 38 hotfix versions, pointing to the correct anchor on their base release page.
Example:
/docs/managed-datahub/release-notes/v_1_0_2→/docs/managed-datahub/release-notes/v_1_0_0/#v102Checklist