Adding version information to the landing page #8642
Merged
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.
Resolves JP-3549
See #8299 #8633
Removing the
stable
branch and allowing RTD to build its own stable documentation has one drawback: the release version (visible under the STScI logo) is replaced with "stable". The release information is written to the HTML<title>...</title>
tag, so it is technically visible to the user, but only barely.This PR displays the release version on the index page. When the stable documentation is generated it will continue to write "stable" below the logo above the navigation pane, however, the user will not need to hunt through the page's source code to find the actual version the documentation relates to.
Demo: https://jwst-pipeline--8642.org.readthedocs.build/en/8642/
Checklist for PR authors (skip items if you don't have permissions or they are not applicable)
CHANGES.rst
within the relevant release sectionHow to run regression tests on a PR