Depend on @jupyter/ydoc instead of @jupyter-notebook/ydoc

[jtpio]

References

Follow-up to jupyter-server/jupyter_ydoc#97

Code changes

Depend on jupyter/ydoc instead of jupyter-notebook/ydoc now that the package has been renamed and published.

User-facing changes

None

Backwards-incompatible changes

A different package will be in the shared scope, but this should only affect alpha releases of 4.0 and 3.6.

[jupyterlab-probot]

Thanks for making a pull request to jupyterlab!
To try out this branch on binder, follow this link:

[jtpio]

Marking as ready, remaining (Python) CI failures are being fixed in #13508

[hbcarlos]

Thanks, @jtpio!

[fcollonval]

@meeseeksdev please backport to 3.6.x

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 3.6.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 27ba0af7842ab369a8da9db8c9b8ddc7150182b5

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #13506: Depend on `@jupyter/ydoc` instead of `@jupyter-notebook/ydoc`'

4. Push to a named branch:

git push YOURFORK 3.6.x:auto-backport-of-pr-13506-on-3.6.x

5. Create a PR against branch 3.6.x, I would have named this PR:

"Backport PR #13506 on branch 3.6.x (Depend on @jupyter/ydoc instead of @jupyter-notebook/ydoc)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.