Sphinx 5 was recently released, and a lot of our repositories have an upper-bound dependency pin that prevents users from installing it. This is an issue for tracking the removal of this upper bound across our repositories.
Repositories that need to be made Sphinx-5 compatible
We have a bunch of repositories, that contain a pin preventing users from using Sphinx 5. This is a checklist to track upgrading/updating them for Sphinx 5 support:
Useful links
Rough checklist for each repo
- Check changelog links above for any relevant changes
- Uncap the version in
setup.py or pyproject.toml in a PR, and re-confirm that the tests pass.
- Double check the docs to make sure that no obvious problems have been introduced in the end-result.
- Merge the PR
- Then make a new release of the repository.
- Then check that box in the meta-issue
- And close the meta-issue when all is finished.
Sphinx 5 was recently released, and a lot of our repositories have an upper-bound dependency pin that prevents users from installing it. This is an issue for tracking the removal of this upper bound across our repositories.
Repositories that need to be made Sphinx-5 compatible
We have a bunch of repositories, that contain a pin preventing users from using Sphinx 5. This is a checklist to track upgrading/updating them for Sphinx 5 support:
myst-nband many other dependencies jupyter-book/jupyter-book#1842https://github.com/executablebooks/sphinx-panels(deprecated)Useful links
Rough checklist for each repo
setup.pyorpyproject.tomlin a PR, and re-confirm that the tests pass.