JupyterLab 3.6.0 Release

[fcollonval]

This is a meta issue to list enhancement candidates for the next minor release 3.6.

• RTC upgraded to the newest API implemented for 4.0.0
  • Remove Yjs locking mechanism #13222
  • Backporting IUser/Collaboration PRs #13242
  • Fix notebook trust in RTC #13274
  • Backport of "Allow empty notebook" (#13141) #13296
  • User service User service #12926
  • File ID optional integration: Use file ID #13246
  • Store document info in the state not in a separate context map out of the document interface. #13317
  • Write documentation about api changes related to RTC for 3.6.0 #13332
  • Add runtime check in collaborative mode for jupyter-server v2 and jupyter-server-ydoc
• Add notification queue and display using toast #12959
• Add announcements #13365
• Store original path as returned from contents API in the Contents.IModel #13216
• release new 1.x lumino and include it to pull Avoid menu layout trashing by moving DOM queries lumino#432 and others
  • Bump Lumino 1.x #13378
• Use settings icons for 6 plugins #13284
• Fix border-radius does not follow css variable #13289
• Avoids restoring widget in dock panel when first loading in 'single-document' mode #13037
  • Reduce ILayoutRestorer API surface area #13300
• Deprecate managing source extensions with jupyter labextension #13321
• Add user configuration for additional schemes for the sanitizer plugin #13341
• Remove some unused CSS styles and fix icon alignment in plugin list #13255
• Add line history (via arrow up/down) to all Stdin widgets in cell outputs #12502

[bollwyvl]

RTC upgraded to the newest API implemented for 4.0.0

And this will require the full server-side yjs stack?

[davidbrochart]

Yes.

[bollwyvl]

Is the runtime dependency on the server still gated behind a collaborative flag, or will the entire experience fail hard without the new server?

[davidbrochart]

Yeah I think that the collaborative flag will make JupyterLab's front-end access the "Y WebSocket", so as long as it doesn't do that I don't think you need the new server.

[mlucool]

Can we backport #12502 to be included here? cc @telamonian

[fcollonval]

Can we backport #12502 to be included here? cc @telamonian

Yes it does not break the API. I'll do the backport

[jtpio]

FYI I started updating to the JupyterLab 3.6 packages downstream in jupyterlite/jupyterlite#876 to help catch potential issues and breaking changes early.

[fcollonval]

Thanks @jtpio

[jtpio]

Opened #13490 which might help fix one.

[jtpio]

Looks like we could make a new 3.6 alpha release now that #13490 has been merged and backported.

Maybe after CI has been stabilized (#13515 and others).

[hbcarlos]

I found some breaking changes in 3.6 that we should fix/document before releasing.
#13551

[jtpio]

For those following this issue, the first 3.6 beta (3.6.0b0) was released two weeks ago: https://github.com/jupyterlab/jupyterlab/releases/tag/v3.6.0b0

[fcollonval]

JupyterLab 3.6.0 has been released