-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.1.1 shows jupyterlab compatibility warning with jupyterlab 4.2 #309
Comments
Relevant output with verbose:
|
I guess we should just graduate 3.0 from alpha (which is compatible with 4.2 and in fact requires 4.2). |
Maybe we should wait with releasing 3.0 until #307 is in. |
Actually we can change the constraint on |
There is still a problem with 2.1.1. When I try to upgrade from 2.1.0 it forces jupyterlab downgrade to 2.1.x. |
Description
Noted on conda-forge/jupyter-collaboration-feedstock#12 (comment), the basic smoke test is failing for whether a user might see (or perceive) problems with their jupyterlab versions. Given the nature and complexity of this extension (and the changes in lab 4.1+), I would surprised if the
4.0.x
versions inyarn.lock
weren't masking some typescript-level issues. Indeed has been pinned, which is suspicious if not also provided as runtime constraints so users' package managers benefit from this wisdom in a meaningful way.Reproduce
https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=930358&view=logs&j=656edd35-690f-5c53-9ba3-09c10d0bea97&t=986b1512-c876-5f92-0d81-ba851554a0a3&l=935
Expected behavior
Context
The text was updated successfully, but these errors were encountered: