New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump to JupyterLab 3.6.0 #898
Conversation
This reverts commit 06c55f0.
This probably goes in conflict with #899 (also in conflict with |
At the end of the JupyterLite workshop last week there were some brief discussions with @fcollonval and @hbcarlos about whether it would be worth updating JupyterLite to JupyterLab 3.6. Since 3.6 mostly brings improvements to RTC, it can also be fine to stick to 3.5 in lite for now since https://github.com/jupyterlite/jupyterlab-webrtc-docprovider still works ok. And focus efforts on updating to lab 4 and nb 7 directly: #826 Although it's still in draft for now, there is a chance the RTC frontend implementation will be making use of an @fcollonval @hbcarlos feel free to add more insights and details here if needed, or in #826. |
I fully agree with @jtpio With the nice drive approach targeting 4 and as our resources are sparse, I advice to skip touching https://github.com/jupyterlite/jupyterlab-webrtc-docprovider before 4. Hence this implies not upgrading JupyterLite to 3.6. |
This works for me! I guess it will then be relevant to continue getting upstream bugfixen to a |
Closing in favor of #1019 as we'll skip the update to JupyterLab 3.6. |
This reverts commit 06c55f0.
References
Superseeds #876
Code changes
Upgrade to 3.6.0 alpha 5
User-facing changes
Use latest version
Backwards-incompatible changes