Skip to content

Latest commit

 

History

History
41 lines (26 loc) · 1.44 KB

RELEASING.md

File metadata and controls

41 lines (26 loc) · 1.44 KB
Raw

Releasing level1c4pps

prerequisites: pip install setuptools twine

  1. checkout master
  2. pull from repo
  3. run the unittests
  4. run loghub and update the CHANGELOG.md file:
loghub foua-pps/level1c4pps --token <personal access token (see https://github.com/settings/tokens)>  -st v<previous version> -plg bug "Bugs fixed" -plg enhancement "Features added" -plg documentation "Documentation changes"

The "--token <personal access token (see https://github.com/settings/tokens)>" somtimes can be excluded.

Paste CHANGELOG.temp to CHANGELOG.md and update RELEASE-VERSION to the version that will be released.

Don't forget to commit!

  1. Create a tag with the new version number, starting with a 'v', eg:
git tag -a v0.1.1 -m "Version 0.1.1"

See semver.org on how to write a version number.

  1. push changes to github git push name-of-foua-pps-repo master --follow-tags

  2. Verify the Github actions unit tests passed

  3. Create a "Release" on GitHub by going to https://github.com/foua-pps/level1c4pps/releases and clicking "Draft a new release". On the next page enter the newly created tag in the "Tag version" field, "Version X.Y.Z" in the "Release title" field, and paste the markdown from the changelog (the portion under the version section header) in the "Describe this release" box. Finally click "Publish release".

  4. Verify the GitHub actions for deployment succeed and the release is on PyPI