Improve Publishing Workflow for Development

[StefanGreve]

Preamble

As discovered in discussion #94, editing the workflow file responsible for the publishing process in a live environment can be a little bit disheartening if there are errors, to put it mildly.

Luckily for us, PyPI provides the facilities to test builds on https://test.pypi.org/. Documentation about that can be found here:

• https://packaging.python.org/en/latest/guides/using-testpypi/

Requirements

Essentially, we need a workflow file that can be manually triggered with the workflow_dispatch event on GitHub actions which requires that the committer updates the __version__ variable in src/anonfile/anonfile.py to major.minor.patch-buildnumber. This makes it much easier to test the release workflow during development, and avoids scenarios in which we have to publish a patch because something went wrong with python-publish.yml.

The secrets for test.pypi.org need to be configured by @nstrydom2 through the repository settings panel. I would propose calling them TEST_PYPI_USERNAME and TEST_PYPI_PASSWORD, respectively.

Planning Status

Scheduled for milestone 1.1.0.