Anthony

The current specifier for Sphinx is https://github.com/readthedocs/sphinx_rtd_theme/blob/master/setup.cfg#L35, so really wide open. We'll want to tune that down to at least avoid bringing in Sphinx 6 and docutils versions we can't...

Ah I see, yeah we use that term fairly loosely I suppose

We'll use this issue to track an actual release going out. We can reassign this issue while you're away, but the actual work behind the release is indeed looking close.

> these are our current direct dependencies: @benjaoming To clarify, those are the current dependencies specified in `master`. Release `1.0.0` has no upper bounds on `Sphinx`: https://github.com/readthedocs/sphinx_rtd_theme/blob/1.0.0/setup.py#L120-L123 The aim of...

I do agree on adding a docutils 0.18 and 0.19 fixes, but this does seem like a good point to split out two separate, smaller releases. Historically, we've been bad...

Changes seem okay technically speaking, but it might be worth double checking on RTD usage first. In theory, old projects might use the common assets still, but we haven't updated...

There are a few arguments for both styles, however npm and the JS community don't have a consistent answer here. I sort of get the argument for putting them in...

The only dependency that really works in this way is jQuery, as we do not bundle jQuery in our artifacts. All of the other packages are used as source files...

> Keeping this in 1.1 if the above is true, otherwise feel free to push to 2.0 Seems like a good fit for 2.0

Python 3 is definitely usable, but you cannot upgrade SASS, Wyrm, or Bourbon. Upgrading these is a known issue, and the fix so far has be to drop the entire...