CI workflow improvements - release-please? #6
Description
Presently, we run wheel building in CI on all of the following:
- PR
- merge to main
- tag (as a precursor to release)
This means that a PR that is merged to main, which is subsequently tagged for release, results in wheels being built three times.
There is some use of caching, e.g. to avoid building the hugr-qis-compiler wheel which takes O(10 minutes) to build. But I would like to do it in a smarter way.
Additionally, I do not like the release workflow:
- Tagging in order to create a release is painful if the release workflow fails.
- There is no verification that the submitted git tag is compatible with the versions of built wheels
- Or that the built wheel versions are indeed greater than the ones on pypi
Instead I would like to consider using release-please or similar. It is not a tool I have used, but it appears to be very useful in the hugr repository.