This project adheres to theSemantic Versioning specification by Tom Preston-Werner.

The actual release (i.e. building the distributions and uploading to PyPI) are automated via GitHub actions.What currently needs to be done manually is updating the changelog and version files.

• Bump version:

  • telegram/_version.py
  • Replace all ocurrences ofNEXT.VERSION by the correct version string in the docstrings
  • if the release includes a Bot API update, updateREADME.rst
  • if the release drops a Python version, updateREADME.rst andpyproject.tolm

• Commit & create a PR

• Make sure that the chango fragment is created correctly for aninternal change. Runchango release --uid vXX.yy and commit the result.

• If all checks pass, squash-merge with the commit message:

  Bump version to v<VERSION> (#<PR-Number>)

• Trigger theworkflow for releasing to PyPI (click "Run workflow" and select the master branch)

• Approve the deployment request for PyPI

• Wait for the GitHub action to finish uploding to PyPI and the GitHub releases page

• Adjust thenew release if necessary:

• OnReadthedocs dashboard check thatlatest,stable and vXX.YY are built correctly

• Close milestones for this version.

• Test in a clean virtualenv thatpip install python-telegram-bot work with the new version.

• If thedoc-fixes branch got merged, create a new one.

• Merge thedev-wiki into theproduction wiki

Please use the following channels/groups to announce a new version release:

• @pythontelegrambotchannel
• @pythontelegrambotgroup (Channel posts are automatically forwarded to here)

Channel posts should be a bit more verbose than the plain release notes. E.g. they can

• list the (non-dev-team) authors, who contributed to the release, maybe even for each PR
• have a short, informative description of new/changed features