Skip to content

Latest commit

 

History

History
68 lines (49 loc) · 1.32 KB

RELEASING.md

File metadata and controls

68 lines (49 loc) · 1.32 KB

Making a Gateway Provisioners Release

Using jupyter_releaser

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

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 commit -a -m "Release ${new_version}"
git tag -a ${new_version} -m "Release ${new_version}"

If building the changelog notes via the releases page (prior to jupyter-releaser) you'll want to push the tags so the changelog generator can know what to reference, otherwise this can be skipped.

git push origin
git push --tags origin
make clean dist

Run tests

make test

Update the version back to dev

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

If tags were not pushed previously (to build changelog) push now.

git push --tags origin

Publish the artifacts to pypi

twine check dist/*
twine upload dist/*