- Renamed project to
docs-versions-menu
(#13) - Changed: Removed support for a config file (#9)
- Dropped support for Python 3.5 and Python 3.6
- Added support for Python 3.10 and 3.11
- Improvements to the workflow and documentation.
- Update of conda-feedstock
The doctr-versions-menu
package was renamed to docs-versions-menu
to reflect that Travis and thus Doctr is no longer a viable option to deploy documentation. Switching from doctr-versions-menu
to docs-versions-menu
requires the following steps:
- Consider switching from Travis to Github Actions
- Update your Sphinx configuration (
conf.py
): - Rename the
doctr_versions_menu_conf
dictionary of settings todocs_versions_menu_conf
. - Change the name of the
doctr_versions_menu
extension in theextensions
list todocs_versions_menu
. - If using a custom
doctr-versions-menu.js_t
template, rename the file todocs-versions-menu.js_t
- Rename the
- Update your Sphinx configuration (
- Update your continuous-integration setup:
- Replace the
doctr-versions-menu
package withdocs-versions-menu
in the project requirements (setup.py
/setup.cfg
) - Replace the installation of the
doctr-versions-menu
package withdocs-versions-menu
in your CI script or environment files - Replace calls to the
doctr-versions-menu
executable with calls todocs-versions-menu
- If using environment variables for configuration, change the
DOCTR_VERSIONS_MENU
prefix toDOCS_VERSIONS_MENU
- Replace the
- For any project using a
doctr-versions-menu.conf
file in thegh-pages
root, set up equivalentDOCS_VERSIONS_MENU_*
environment variables
To ease migration, the new docs-versions-menu
will still process doctr_versions_menu_conf
, DOCTR_VERSIONS_MENU
environment variables, and a doctr-versions-menu.js_t
template, while emitting a warning. This limited backwards-compatibility may be removed in later versions.
Note: this release was under the project name doctr-versions-menu.
- Fixed: The
doctr-versions-menu
exectuable no longer fails when run outside of a git repository (#15, thanks to Alexander Blech) - Fixed: Custom
doctr-versions-menu.js_t
template were being ignored (#18)
Note: this release was under the project name doctr-versions-menu.
- Added: The label in the top left corner of the version menu can now be configured in
conf.py
(settingmenu_title
). - Added:
--default-branch
option,<default-branch>
group for folder specifications, anddefault-branch
field inversions.json
(#12) - Changed: The default
--versions
now uses<default-branch>
, automatically picking up on either "master" or "main" as the default branch (#12) - Changed: The default template for
index.html
now automatically forwards to the default-branch (based on the--default-branch
option, instead of just "master"), or the first available branch if there is no released version (#12)
This release addresses two major compatibility issues:
- Both git and Github have recently switched the name of the default branch from "master" to "main". This release adds support for new projects using "main" as their default branch.
- As of December 2020, Travis CI has stopped their support for open source. Consequently, Doctr can no longer be used to deploy documentation at no cost. This release adds rudimentary support for deploying the documenation with Github Actions instead of Doctr, see Deployment with Github Actions.
Note: this release was under the project name doctr-versions-menu.
- Added:
--no-downloads-file
option,downloads_file = False
in config. (#4, thanks to Tyler Pennebaker) - Fixed:
versions.py
ongh-pages
branch was not being committed (#5) - Fixed: Compatibility with any
pyparsing
version>= 2.0.2
(#8, thanks to Hugo Slepicka) - Added: The
doctr-versions-menu
executable can now be configured through environment variables. This allows to keep configuration on the source branch, in the.travis.yml
file (#6, thanks to Tyler Pennebaker) - The Doctr Versions Menu package can now be installed via conda (thanks to Hugo Slepicka)
Note: this release was under the project name doctr-versions-menu.
- Added:
--versions
option for customizing which folders appear in the versions menu and in which order. - Added:
--label
option for customizing the labels appearing the versions menu - Added:
--warning
option for customizing on which folders specific warnings are displayed - Added:
--latest
option for configuring which folder is the "latest stable release" - Added: Write a script
versions.py
to the root of thegh-pages
branch (--write-versions-py
option) - Changed: unreleased and pre-released versions now show different warnings by default
- Changed:
index.html
template is now rendered with fullversion_data
- Changed: development/pre-release versions now longer have the "dev" suffix in the versions menu by default
- Changed: The versions menu now uses the same ordering of versions as Read-the-Docs, by default: the folders are ordered from most current to least current.
- Changed: internal format of
versions.json
- Removed:
--default-branch
option. This is replaced by the new--latest
option and enhanced template rendering of theindex.html
- Removed:
--suffix-unreleased
option. This can now be achieved via the--label
option
This is a major release that breaks backwards compatibility.
Specifically, due to the changes in versions.json
, when upgrading from older versions, it
may be necessary to replace doctr-versions-menu.js
files in existing
folders in a project's gh-pages
branch.
- Initial release of doctr-versions-menu.