Bump jupyter-lsp from 2.2.0 to 2.2.2 in /utilities/project_planning

[dependabot]

Bumps jupyter-lsp from 2.2.0 to 2.2.2.

Changelog

Sourced from jupyter-lsp's changelog.

jupyter-lsp 2.2.2

• bug fixes:
  • address warning about renamed extension_points (#1035)
  • fix compatibility with jupyter server 1.x
  • fix an authentication-related security vulnerability (see the advisory for details)
• enhancements:
  • add authorization support (lsp resource, jupyter-server v2+ only) - this allows server operators for fine grained access control, e.g. in case if specific users (such as guest or read-only users) should not be allowed to access LSP; this is in addition to authentication fixes

@jupyter-lsp/jupyterlab-lsp 5.0.1

• bug fixes:
  • fix false “undefined name” in %%time and %%capture magics #1007 (thanks @​i-aki-y!)
  • fix completion items for paths and other long items being cut off #1025
  • workaround issue with markdown lost on edit #1016
  • fix latex/Greek letters insertion and other completions which do not match prefix (do not pre-filter completions from kernel) #1022
  • fix completions in Console #1023
  • fix customising priority after pre-setting it with overrides.json #1027
  • fix jump to definitions in a file inside root in Pyright on Windows #1024
  • fix typos in setting title and help message #999 and #1010
• maintenance:
  • fix bootstrap script #1021
  • bump axios from 1.2.1 to 1.6.2 #1019
  • bump @​babel/traverse from 7.22.5 to 7.23.4 #1020

jupyter-lsp 2.2.1

• bug fixes:
  • use APIHandler over JupyterHandler to get CORS OPTIONS #952 (thanks @​zhanba!)
  • use shutil.which to discover npm executable on Windows (thanks @​jameshurst!)
• maintenance:
  • resolve traitlets type warnings, lint, remove six #1015
  • use sys.executable in stdio tests #998

@jupyter-lsp/jupyterlab-lsp 5.0.0

• enhancements:
  • uses toast notifications instead of messages on status bar
  • diagnostics panel will be re-opened on reload
• maintenance:
  • support JupyterLab 4
  • use upstream @jupyterlab/lsp package
  • use camelCase convention in TypeScript/JavaScript code
  • use @codemirror/linter to show diagnostics
    • this comes with a different style of underlines and custom tooltips
• known issues/limitations:
  • configuration of language servers via JSON Settings Editor may result in a spurious warning due to a transitive clash with settings from the UI editor when using nested pattern (e.g. {pylsp: {flake8: {enabled: true}}}); the dotted pattern (e.g. {"pylsp.flake8.enabled": true}) does not lead to such problem.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.