You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Remove upperbound on sphinx
* Explain that we don't test old releases against future releases of our dependencies
* Clarify Sphinx policy
Co-authored-by: Chris Holdgraf <[email protected]>
Co-authored-by: Chris Holdgraf <[email protected]>
Copy file name to clipboardExpand all lines: docs/contribute/topics.md
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -212,6 +212,16 @@ The output of the last command includes:
212
212
- a short summary of the current state of the accessibility rules we are trying to maintain
213
213
- local paths to JSON and HTML reports which contain all of the issues found
214
214
215
+
## Update support for new Sphinx versions
216
+
217
+
This theme does not pin the upper version of Sphinx that it supports, but there may be changes that need to happen when Sphinx releases a new version.
218
+
As a general rule, we try to support new major Sphinx versions within 6 months of its release.
219
+
220
+
Here's a list of things to check when Sphinx releases a new version:
221
+
222
+
-[Look at the Sphinx Changelog](https://www.sphinx-doc.org/en/master/changes.html) and make sure there are no obvious breaking changes.
223
+
-[Look at the deprecated API changes](https://www.sphinx-doc.org/en/master/extdev/deprecated.html) and make sure there are no obvious breaking changes.
224
+
215
225
## Update our kitchen sink documents
216
226
217
227
The [kitchen sink reference](../demo/kitchen-sink/index.rst) is for demonstrating as much syntax and style for Sphinx builds as possible.
0 commit comments