Skip to content

Latest commit

 

History

History
56 lines (39 loc) · 1.13 KB

RELEASING.md

File metadata and controls

56 lines (39 loc) · 1.13 KB
  1. Set release information
export PREVIOUS_RELEASE=$(git describe --abbrev=0)
export NEW_RELEASE=0.5.1
  1. Update the version number
poetry version $NEW_RELEASE
  1. Generate changelog since the last release
# gem install github_changelog_generator --pre
export CHANGELOG_GITHUB_TOKEN=token
~/.gem/ruby/2.4.0/bin/github_changelog_generator --user rytilahti --project python-miio --since-tag $PREVIOUS_RELEASE --future-release $NEW_RELEASE -o newchanges
  1. Copy the changelog block over to CHANGELOG.md and write a short and understandable summary.

  2. Commit the changed files

git commit -av
  1. Tag a release (and add short changelog as a tag commit message)
git tag -a $NEW_RELEASE
  1. Push to git
git push --tags
  1. Upload new version to pypi

If not done already, create an API key for pypi (https://pypi.org/manage/account/token/) and configure it:

poetry config pypi-token.pypi <token>

To build & release:

poetry build
poetry publish
  1. Click the "Draft a new release" button on github, select the new tag and copy & paste the changelog into the description.