You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
some logic to bump the dependency on the jupyterlab Python package. At least when we update to a new minor version. Or make that configurable in the workflow.
handle pre-release cycles. Currently main is on JupyterLab 4.4.0a1, but the latest version as retrieved by the script will be 4.3.4. So it should first check if the target branch is using a pre-release, and make sure updates are for newer versions
we should ideally be able to run the workflow for other backport branches to, for example to update 7.3.x while main is still targeting 7.4.0
Tracking improvements for the workflow to update to newer JupyterLab versions: https://github.com/jupyter/notebook/actions/workflows/upgrade-juypterlab-dependencies.yml
The workflow was originally added in #7281.
github-actions
user to open the PRjupyterlab
Python package. At least when we update to a new minor version. Or make that configurable in the workflow.notebook/pyproject.toml
Line 2 in c0ddf01
notebook/pyproject.toml
Line 35 in c0ddf01
Example PR which updated to a patch release: https://github.com/jupyter/notebook/pull/7527/files
The text was updated successfully, but these errors were encountered: