GRO-951-1 Make variable docs content render client-side [version info] - #1328
Open
bpander wants to merge 9 commits into
Open
GRO-951-1 Make variable docs content render client-side [version info]#1328bpander wants to merge 9 commits into
bpander wants to merge 9 commits into
Conversation
… with up-to-date data
…n't get stale when we stop rebuilding old versions every deployment
…e of its logic with VersionSelector
…ates for /docs/latest (e.g. include for /docs/v0.63 when v0.63 is the latest version just in case a version goes straight from the most recent to unsupported (unlikely but technically possible))
bpander
added this pull request to stack #1329
September 11, 2026 19:28
bpander
marked this pull request as ready for review
September 11, 2026 20:29
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.
GRO-951
We're going to stop building old versions of docs (for the most part). But a version picker on a page from say v0.44 will still need to include new versions and up-to-date LTS/Supported info. This PR is mainly for that.
We also have version info boxes which currently include references to the latest version. Those will also become stale on old (archived) versions. We could theoretically omit the latest version there too, but it seemed easy enough to update as long as we were already fetching version info for the dropdown.
The meat of this PR is
src/components/chrome/utils/versionUtils.ts+src/pages/docs/versions.json.ts, most everything else is just jekyll->astro conversions.