Fix docs version selector to include beta prereleases #60753 #60805
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.
Problem
The documentation version selector currently only includes RC prereleases. As a result, beta (and alpha) documentation—such as v1.13.0-beta1 —is omitted whenever dev docs (e.g. v1.14.0-dev) are present, even though the beta documentation exists online.
This issue has affected multiple releases (e.g. 1.10, 1.13) and leads users to believe that beta documentation is missing.
Solution
This PR updates the prerelease selection logic in Documenter.Writers.HTMLWriter.expand_versions to:
The change is minimal and localized to
julia/doc/make.jl.Verification
The logic was verified via static inspection and scenario simulation:
Resulting selector order:
v1.12 → v1.13.0-beta1 → v1.14.0-dev
AI Usage Disclosure
AI tools were used to assist with understanding the existing code, exploring edge cases, and reviewing logic.
All code changes were written, reviewed, and validated by the me .
Related issues
Fixes #60753
Related to #50872