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

Prepare jupyterlab-lsp 3.9.3 release #727

Merged
merged 4 commits into from
Dec 19, 2021
Merged

Prepare jupyterlab-lsp 3.9.3 release #727

merged 4 commits into from
Dec 19, 2021

Conversation

krassowski
Copy link
Member

Minor patch for jupyterlab/language-packs#198 and dev/testing dependencies refresh.

@github-actions
Copy link

Binder 👈 Launch a binder notebook on branch jupyter-lsp/jupyterlab-lsp/v3.9.3

@krassowski krassowski force-pushed the v3.9.3 branch 2 times, most recently from bf79348 to ce2aca0 Compare December 19, 2021 15:35
@krassowski krassowski merged commit 5f5054c into master Dec 19, 2021
@krassowski krassowski deleted the v3.9.3 branch December 19, 2021 17:44
@bollwyvl
Copy link
Collaborator

@krassowski sorry, was noticing this on my phone while running around, but didn't have a time to chime in: the bump of the minimum python did land on both jupyterlab-lsp (which got a minor bump) and on jupyter-lsp which didn't even get that .

I guess on conda-forge, I guess I'll just not bump the jupyter-lsp build number...

@krassowski
Copy link
Member Author

Good catch; I updated release notes to mention this. I mean EOL is this week. jupyter-lsp artifacts were not uploaded (cannot upload new one with the same version) so no need to worry about it I think. jupyterlab-lsp indeed will complain on Python 3.6 if someone tries to install 3.9.3.

@bollwyvl
Copy link
Collaborator

Yeah, no harm no foul, i think.

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