once its established that the azure-buildwheels pipeline works the release process can be further simplified by an automatic upload of a new release to pypi. I see two possibilities to realize this:
1) a dedicated release pipeline which is triggered manually after checking that the automatically run cibuildwheels pipeline succeeds (this is currently my preferred option)
2) include the pypi upload in the existing cibuildwheels pipeline as optional step if a new version tag (refs/tags/v*) is found.
This is the last piece to streamline making a new release and should considerable simplify maintenance.
once its established that the azure-buildwheels pipeline works the release process can be further simplified by an automatic upload of a new release to pypi. I see two possibilities to realize this:
1) a dedicated release pipeline which is triggered manually after checking that the automatically run cibuildwheels pipeline succeeds (this is currently my preferred option) 2) include the pypi upload in the existing cibuildwheels pipeline as optional step if a new version tag (
refs/tags/v*
) is found.This is the last piece to streamline making a new release and should considerable simplify maintenance.