Open lincior opened 1 year ago
Opted for the default workflow, suggested here: python package is published to PyPI on each Release.
Added a manual trigger for uploading to TestPyPI.
A possible process would be using branches with naming convention release/*
to start triggering actions like a semantic versioning trigger, pre-release build and publish...
Define the release process for this package.
Upload to PyPI should happen when a GitHub Release is created (which needs a tag?). How to manage pre-release versions though?