-
Notifications
You must be signed in to change notification settings - Fork 207
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
Upgrading notebook and jupyterlab version #2524
Conversation
Signed-off-by: Sachin Pisal <spisal@nvidia.com>
Signed-off-by: Sachin Pisal <spisal@nvidia.com>
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
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.
LGTM
I will wait for the working deployment pipeline before merging this one. Thanks @1tnguyen. |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Seems like the deployment will most probably work. So will merge this PR now. |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
I think we may have (partially) identified the root cause for why the deployment isn't working (Ubuntu base VM image updates for our runner independent of the GitHub runners application that sits on top of that image), but just FYI to all, these were done with temporary runners that the main branch is not currently using, so main branches will still fail until we identify the best path forward. |
Fix for exception id EXC-VZVQ-PUQE which consists of the following vulnerability
GHSA-9q39-rmj3-p4r2
Affected libraries are
jupyterlab
notebook
Fix given in: GHSA-9q39-rmj3-p4r2