release v0.12.0

doc/source/development.rst

@@ -155,18 +155,17 @@ for PyPI first before publishing a final release.
 - when all tests pass locally and via GitHub Actions, update the test coverage report by running ``make cov_tests``
   locally
 
-4. Publish package to PyPI:
+4. Publish package to PyPI and GitHub:
 
+- make a new tag for the new version via ``git tag -a vX.Y.Z -m "version X.Y.Z"``
+- push the new tag to the GitHub repository – this will automatically trigger the release workflow and publish the
+  source and built distributions to PyPI
 - build source distribution via ``make sdist``
 - build wheel via ``make wheel``
-- check both via ``twine check dist/...``
-- if checks passed, upload both to PyPI via ``twine upload dist/...``
+- create a new release from the tag in the GitHub repository and upload the source and wheel distributions
 
-5. Finalization
+5. Finalization:
 
-- make a new tag for the new version via ``git tag -a vX.Y.Z -m "version X.Y.Z"``
-- push the new tag to the GitHub repository
-- create a new release from the tag in the GitHub repository
 - merge the development or release branch with the master branch and push the master branch to the GitHub repository
 - log in to `readthedocs.org <https://readthedocs.org/>`_, go to the project page, activate the current version, let
   it build the documentation

setup.py

@@ -11,7 +11,7 @@
 from setuptools import setup, find_packages
 
 __title__ = 'tmtoolkit'
-__version__ = '0.12.0rc3'
+__version__ = '0.12.0'
 __author__ = 'Markus Konrad'
 __license__ = 'Apache License 2.0'
 

tmtoolkit/__init__.py

@@ -8,7 +8,7 @@
 import logging
 
 __title__ = 'tmtoolkit'
-__version__ = '0.12.0rc3'
+__version__ = '0.12.0'
 __author__ = 'Markus Konrad'
 __license__ = 'Apache License 2.0'