Skip to content

Latest commit

 

History

History
133 lines (103 loc) · 4.32 KB

RELEASE.md

File metadata and controls

133 lines (103 loc) · 4.32 KB
Raw

Making a JupyterLab release

This document guides a contributor through creating a release of JupyterLab.

Check installed tools

Review CONTRIBUTING.md. Make sure all the tools needed to generate the built JavaScript files are properly installed.

Creating a full release

We publish the npm packages, a Python source package, and a Python universal binary wheel. We also publish a conda package on conda-forge (see below). See the Python docs on package uploading for twine setup instructions and for why twine is the recommended method.

Publish the npm packages

The command below ensures the latest dependencies and built files, then prompts you to select package versions. When one package has an effective major release, the packages that depend on it should also get a major release, to prevent consumers that are using the ^ semver requirement from getting a conflict.

jlpm run publish

Publish the Python package

  • Update jupyterlab/_version.py with an rc version
  • Prep the static assets for release:
jlpm run build:update
  • Commit and tag and push the tag
  • Create the Python release artifacts:
rm -rf dist
python setup.py sdist
python setup.py bdist_wheel --universal
twine upload dist/*
  • Test the rc in a clean environment
  • Make sure the CI builds pass
    • The build will fail if we publish a new package because by default it is private. Use npm access public @jupyterlab/<name> to make it public.
    • The build will fail if we forget to include style/ in the files: of a package (it will fail on the jupyter lab build command because webpack cannot find the referenced styles to import.
  • Update the other repos listed below
  • Update the extension examples listed below
  • Update the xkcd tutorial
  • Update jupyterlab/_version.py with a final version
  • Make another Python release
  • Create a branch for the release and push to GitHub
  • Merge the PRs on the other repos and set the default branch of the xckd repo
  • Publish to conda-forge (see below)
  • Update jupyterlab/_version.py with a dev version
  • Commit and push the version update to master
  • Release the other repos as appropriate

Other repos to update

Extension examples to update

Updating the xkcd tutorial

  • Create a new empty branch in the xkcd repo.
git checkout --orphan name-of-branch
git rm -rf .
git clean -dfx
cookiecutter path-to-local-extension-cookiecutter-ts
# Fill in the values from the previous branch package.json
cp -r jupyterlab_xkcd .
rm -rf jupyterlab_xkcd
  • Create a new PR in JupyterLab.
  • Run through the tutorial in the PR, making commits and updating the tutorial as appropriate.
  • Prefix the new tags with the branch name, e.g. 0.28-01-show-a-panel
  • For the publish section of the readme, use the LICENSE and README files from the previous branch, as well as the package.json fields up to license.
  • Push the branch and set it as the default branch for the tutorial repo.
  • Submit the PR to JupyterLab

If you make a mistake and need to start over, clear the tags using the following pattern:

git tag | grep 0.xx | xargs git tag -d

Publishing to conda-forge

  • Get the sha256 hash for conda-forge release:
shasum -a 256 dist/*.tar.gz

Making a patch release of a JavaScript package

  • Backport the change to the previous release branch
  • Make a new PR against the previous branch
  • Run the following script, where the package is in /packages/package-folder-name:
jlpm run patch:release package-folder-name
  • Push the resulting commit and tag.
  • Create a new Python release on the previous branch
  • Cherry pick the patch commit to the master branch