Open tfagerlind opened 2 years ago
This page describes a popular method that make automatic releases for every made tag:
It is based on the possibility to add a trusted publisher to pypi
It seems to assume that the version is already set by setup.py or similar, but perhaps that behavior can be tweaked somehow
One thing that bugs me is that I don't understand how the upload to test-pypi could possibly work for every push. Assuming that the approach uses a version somehow defined in a commit, the user would have to change it for every push. Otherwise test-pypi won't allow a release in the general case since it is not possible to upload the same version twice (right?)
Perhaps it is possible to use gitpython to retrieve the version from the tag system and add a random number in the testpypi case. However I'm not sure I would like to do that, since then I would like to use verso itself and that kind of boot strapping makes me uneasy.
Using the publisher feature in pypi requires 2fA
We should compare the solution above with https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases and perhaps combine it.
Grupping CHANGELOG could actually be a viable alternative for Verso
The current delivery to PyPI is manual:
version=X.Y.Z make upload-test
is manualversion=X.Y.Z make upload-prod
is manualStill unclear to me how all these steps should be automated. One thing todo is to look what the release-feature of github does