We use semantic versioning.
Once there are enough changes in master
, we can release a new version
- Checkout the development branch:
git checkout master
- Make sure it's up-to-date with the remote:
git pull
- Create the release branch:
git checkout -b rel-x.y.z
, wherex.y.z
is the new version of the package. - Set the new version:
poetry version x.y.z
. - Add these changes:
git add -u
- Commit these changes:
git commit -m "Bump andz version to x.y.z"
- Push them to the remote:
git push --set-upstream origin rel-x.y.z
- Create a PR and ask for code review
- Once the PR has been approved, merge
rel-x.y.z
intomaster
- Create a new tag
git tag x.y.z
- Push it to the remote
git push origin --tags
, which triggers the GitHub workflow that releases the package to PyPI