Can't package jupyter-ydoc 1.1.1 with jupyter-collaboration 1.2.1 about jupyter_ydoc

[davidbrochart]

1. jupyter-collaboration v2 and jupyter-ydoc v2 require pycrdt which is declared to be not ready for production yet

Ypy was not more ready for production, on the contrary. You shouldn't be worried about that.

Number 2 and 3 conflict with each other. Any advice?

I can release jupyter-ydoc v1.2.1 with a test requirement ypy-websocket>=0.12.1,<0.13.0, what do you think?

[bnavigator]

I tried running the test suit on 1.1.1 with ypy-websocket 0.12 and it failed.

If it's better to ignore the incubation phase warning and just update jupyter-collaboration and jupyter-ydoc to v2, I see no use in a jupyter-ydoc 1.2.1. I wonder what's the use of the backport releases and the 1.x branch in jupyter-collaboration then.

[davidbrochart]

I recommend upgrading jupyter-collaboration and jupyter-ydoc to v2 anyway, yes.
Backports are always good for dependencies which cannot upgrade, but it's still better to upgrade if you can.

[bnavigator]

Thank you for the clarification.

I had to package y-py 0.7.0a1, which is nominally an alpha version, in order to enable the test suite for pycrdt. But I guess that is fine since there are no other consuming packages for it anyway.