maint, breaking: drop support for jupyterlab 2 #394
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
manics
reviewed
Apr 14, 2023
|
Can start testing with betas, but otherwise who knows?
|
manics
approved these changes
Apr 18, 2023
|
Going for a merge and a changelog PR to get moving on the release efforts! |
15 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this PR, the JupyterLab extension will still be published as an NPM package to @jupyterhub/jupyter-server-proxy, but we will not test against it or ensure future functioning, or document how to install it etc. Dropping support for jupyterlab 2 was proposed to go with the 4.0.0 release planned in #388 as jupyterlab 4 is coming out and we are to support both jupyterlab 3 and 4 already.