Releasing

jupyterlab-lsp and jupyter-lsp releases may require building both the python package and nodejs packages.

Updating Version Strings

Use the bump_versions script to manage the version strings:

python scripts/bump_versions.py

Check the version strings across the various files:

python scripts/integrity.py

  • TODO: create a release.py script #88

The PyPI version (jupyter-lsp) must be updated in the following places:

  • py_src/jupyter_lsp/_version.py (canonical)

  • .github/workflows/job.test.yml

  • CHANGELOG.md

The npm version of jupyterlab-lsp must be updated in the following places:

  • packages/jupyterlab-lsp/package.json > version (canonical)

  • .github/workflows/job.test.yml

  • packages/metapackage/package.json

  • CHANGELOG.md

The npm version of lsp-ws-connection must be updated in the following places:

  • packages/lsp-ws-connection/package.json > version (canonical)

  • packages/jupyterlab-lsp/package.json

  • CHANGELOG.md

The JupyterLab version (if a newer is supported or required) needs to be updated in:

  • packages/jupyterlab-lsp/package.json > devDependencies > @jupyterlab/application (canonical)

  • binder/environment.yml

  • requirements/lab.txt

  • .github/workflows/job.test.yml

  • README.md

Releasing:

cd packages/lsp-ws-connection
npm publish --access public
cd -
cd packages/completion-theme
npm publish --access public
cd -
cd packages/theme-material
npm publish --access public
cd -
cd packages/theme-vscode
npm publish --access public
cd -
cd packages/jupyterlab-lsp
npm publish --access public
cd -
./scripts/publish_pypi.sh