pypi has a Github action to publish software releases on pypi. At the moment we are already running tests using Github actions which runs the tests against a Cloud hosted Command Centre (running in AWS).
The suggested release lifecycle should be
A developer has a pull request for the next set of feature changes
All tests run and pass
Documentation is compiled and published using the Github action
A version is tagged using semver conventions
Release notes are published as a Github release
Upon the release going out a job is triggered to publish the package onto pypi
Update local tags and documentation with the links (if applicable)
pypi has a Github action to publish software releases on pypi. At the moment we are already running tests using Github actions which runs the tests against a Cloud hosted Command Centre (running in AWS).
The suggested release lifecycle should be
semver
conventions