-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Update to JupyterLab 4.0.0a31 #350
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2022.11.18.09.29.52
@@ -33,8 +33,7 @@ requirements: | |||
- jinja2 >=3.0.3 | |||
- jupyter_core | |||
- jupyter-lsp >=1.5.1 | |||
- jupyter_server >=1.16.0,<3 | |||
- jupyter_ydoc >=0.2.0,<0.3.0 | |||
- jupyter_server >=2.0.0rc3,<3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be blocking on jupyter_server
2 to be available on conda.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this will need to add the jupyter_server_rc
channel:
https://github.com/conda-forge/jupyter_server-feedstock/pull/102/files#diff-999d2f034982a9a29cc0f5a5340497f76ff9243576ea74e5954ec5ad5f32b74cR6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@conda-forge-admin please rerender |
…nda-forge-pinning 2022.11.18.17.56.12
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was not passing and not merged. |
Afk, but:
jupyterlab 4.0.0a31 has requirement jupyter-server-ydoc<0.5.0,>=0.4.0, but
you have jupyter-server-ydoc 0.1
…On Fri, Nov 18, 2022, 17:03 github-actions[bot] ***@***.***> wrote:
Hi! This is the friendly conda-forge automerge bot!
I considered the following status checks when analyzing this PR:
- *linter*: passed
- *azure*: failed
Thus the PR was not passing and not merged.
—
Reply to this email directly, view it on GitHub
<#350 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALCRGGZEQQU4AOVJWMZGDWJADNNANCNFSM6AAAAAASEKSIGM>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bump jupyter server ydoc
Hi! This is the friendly conda-forge automerge bot! Commits were made to this PR after the |
oof this depedency stack (heap? mound?) is not giving me warm feelings. |
While we could theoretically just add that dependency, i think it's more important the stack of already-shipped deps is solid rather than getting an alpha out within some specific timeframe... |
@conda-forge-admin please restart ci
|
Some observations:
|
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)