Daniel McCloy

Also since there's a very easy workaround (just one line change to `conf.py`) I'm comfortable removing the `block-release` tag on this one.

tagging @hoechenberger who may be interested in this discussion too

I will try to have a look tomorrow or friday. after that I'm at a project-specific hackathon the following week, so may need to pass the baton.

ditto for MNE-Python:  Here is how we do it: https://mne.tools/versionwarning.js

I agree that version warnings need/deserve a dedicated banner. For example, ours has some JS that tries to make the link go to the corresponding docs page in the stable...

ha, good catch. I'm actually not sure if this is working or not for MNE-Python because I didn't backport the theme's switcher to our stable docs, but I suspect that...

to say something a bit more coherent about this: The problem that I think has been revealed here is that the `version` value of a given entry in `versions.json` needs...

I like this idea in principle, but in practice it might be non-trivial for theme users to adapt to this change. For example, in MNE-Python's theme customizations we make use...

We have something like that in MNE, I can implement if you want. If you can point to which test(s) you want timed that would help.

Agreed.