Skip to content

Latest commit

 

History

History
26 lines (21 loc) · 820 Bytes

RELEASE.md

File metadata and controls

26 lines (21 loc) · 820 Bytes

Releasing to PyPI

Releasing to PyPI happens via Github Actions CI. In order for a PyPI deployment to occur, a new tag must be pushed to the master branch. So, if you have setup your git to push to this reposository, in order to deploy the latest changes from devel, you need to run:

git checkout master
git merge --ff-only devel
git push origin master
git tag <next-version>
git push origin <next-version>

Versioning

We use the SemVer specification:

Given a version number MAJOR.MINOR.PATCH, increment the:

  1. MAJOR version when you make incompatible API changes,
  2. MINOR version when you add functionality in a backwards compatible manner, and
  3. PATCH version when you make backwards compatible bug fixes.