I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
The last approach got blocked as we have branch protection.
This approach creates a PR from the github actions bot after a release is made with the changes to the code.
See e.g. #788.
Refactored to use only one workflow.
The steps are:
Check for version update
(If update available): Build and test
Release to PyPI
Create PR
Next up is pyvespa release, which will need a slightly different approach.
I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
The last approach got blocked as we have branch protection. This approach creates a PR from the github actions bot after a release is made with the changes to the code. See e.g. #788.
Refactored to use only one workflow.
The steps are:
Next up is pyvespa release, which will need a slightly different approach.