Skip to content

Latest commit

 

History

History
52 lines (37 loc) · 1.02 KB

RELEASE.md

File metadata and controls

52 lines (37 loc) · 1.02 KB

Making a Jupyter Server Release

Using jupyter_releaser

The recommended way to make a release is to use jupyter_releaser.

Note that we must use manual versions since Jupyter Releaser does not yet support "next" or "patch" when dev versions are used.

Manual Release

To create a manual release, perform the following steps:

Set up

pip install hatch twine build
git pull origin $(git branch --show-current)
git clean -dffx

Update the version and apply the tag

echo "Enter new version"
read new_version
hatch version ${new_version}
git tag -a ${new_version} -m "Release ${new_version}"

Build the artifacts

rm -rf dist
python -m build .

Update the version back to dev

echo "Enter dev version"
read dev_version
hatch version ${dev_version}
git push origin $(git branch --show-current)

Publish the artifacts to pypi

twine check dist/*
twine upload dist/*