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 Jupyterlab 3.0 dependencies after official release #1076

Closed
2 tasks
ajbozarth opened this issue Nov 16, 2020 · 1 comment · Fixed by #1167
Closed
2 tasks

Update Jupyterlab 3.0 dependencies after official release #1076

ajbozarth opened this issue Nov 16, 2020 · 1 comment · Fixed by #1167
Assignees
Labels
external:jupyterlab 3.0 external:Upstream Depended on deliverables in other repos outside the elyra org
Milestone

Comments

@ajbozarth
Copy link
Member

ajbozarth commented Nov 16, 2020

Once JupyterLab 3.0 is released we will need to make the following updates related to dependencies

  • remove --pre from pip installs in .github/workflows/pythonapp.yml and etc/scripts/clean-jupyterlab.sh
  • Update all package.json files to remove rc from the lab packages versions
@ajbozarth ajbozarth added this to the 2.0.0 milestone Nov 16, 2020
@ajbozarth ajbozarth self-assigned this Nov 16, 2020
@lresende lresende added external:Upstream Depended on deliverables in other repos outside the elyra org and removed status:Needs Triage labels Nov 17, 2020
@lresende lresende changed the title Jupyterlab 3.0 release clean up Update Jupyterlab 3.0 dependencies after official release Nov 17, 2020
@ajbozarth
Copy link
Member Author

related, we will need to switch to using jupyter-resource-usage rather just just depending on nbdime since the resource status bar item was moved into a separate extension in jupyter-server/jupyter-resource-usage#69

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external:jupyterlab 3.0 external:Upstream Depended on deliverables in other repos outside the elyra org
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants