`sphinx-thebe` `0.3.0-rc.0` to enable testing of `thebe 0.9.0-rc.x`

[stevejpurves]

thebe has a release candidate available for testing, but jupyterbook and sphinx-thebe users cannot access it yet.

Should we release an rc tagged version of sphinx-thebe that allow people to upgrade and test?

See https://www.npmjs.com/package/thebe?activeTab=versions for latest thebe versions.

Right now thebe 0.9.0-rc.5 is available, which would be available on the following unpkg.com urls:

• https://unpkg.com/thebe@0.9.0-rc.5/lib/index.js
• https://unpkg.com/thebe@0.9.0-rc.5/lib/thebe.css

But ideally, we could have sphinx-thebe point to an unpinned rc version of thebe, making it easy to push out fixes via new release candidates.

This can be done by just using the rc tag in place of the full semantic version in the url, i.e.:

• https://unpkg.com/thebe@rc/lib/index.js
• https://unpkg.com/thebe@rc/lib/thebe.css

[stevejpurves]

cc @mmcky

[psychemedia]

Is all that's required to get this working with thebe updates to the thebe package versions? Or is there plumbing underneath that needs updating? Eg notifications that say "opening with jupyterlite" (or are those UI issues handled by thebe itself?)

[psychemedia]

Is there a demo repo anywhere that demonstrates a minimum viable use of sphinx-thebe being used in a Jupyter Book context to run code on a JupyterLite kernel, eg via GitHub Actions workflow publishing simple content to GitHub Pages? [@stevejpurves @rowanc1 ?]