Pin ydoc to ^3.0.2 (>=3.0.2,<4) to deliver fixes to users

[andrii-i]

Description

jupyter-ydoc v3.0.2 fixed jupyterlab/jupyterlab#16934.

Currently jupyterlab packages ydoc pin it at ^3.0.0 which is the same as >=3.0.0,<4 so environments with ydoc 3.0.0, 3.0.1 installed or cached would not get this update.

Proposed solution

Pin jupyter_ydoc to ^3.0.2 (>=3.0.2,<4).

I'll be happy to open a PR if community thinks it's a good solution.

[krassowski]

• v3.0.2 contains exclusively changes in the python package
• JupyterLab does not depend on the jupyter-ydoc python package
• even if the changes were in the npm package, changing version ranges in npm @jupyterlab/* packages would not make that much of a difference for users (but it would for extension authors) because it is the version in yarn lock that matters

Given the above I wonder if this issue would be better discussed in jupyter-collaboration repository where there are python packages which do depend on jupyter-ydoc.

[andrii-i]

Fixed by #412 released as a part of v3.1.0beta0 that pins "jupyter_ydoc>=2.1.2,<4.0.0,!=3.0.0,!=3.0.1"

Thank you for suggestions @krassowski, all on point.