Skip to content
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 dependencies to be compatible with JupyterLab 4.x #227

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

lresende
Copy link
Member

@lresende lresende commented Jan 2, 2024

Developer's Certificate of Origin 1.1

   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Signed-off-by: Luciano Resende <[email protected]>
Signed-off-by: Luciano Resende <[email protected]>
Signed-off-by: Luciano Resende <[email protected]>
Signed-off-by: Luciano Resende <[email protected]>
@karlaspuldaro
Copy link
Member

We need a detailed issue for migration to JupyterLab 4, to keep track of all required steps, this PR could be step one.
In my opinion, it would be best to plan the steps more carefully, so they're better isolated. Changing all dependencies at once can affect everything, and the changes become complex too quickly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants