Run workflow on "release" branches

[lenkan]

Currently. Workflows are not being run on pushes to release branches "v*". I suggest to add "v*" to the branch filter in the workflow. Any thoughts?

Alternatively, use branch name pattern "release/vx.y.z" and put "release/*" in the branch pattern in the workflow to avoid running workflow on branches starting with "v".

See here https://github.com/WebOfTrust/keripy/actions?query=branch%3Av1.3.0

[lenkan]

Actually. I found in the discussion for branching strategy that we are supposed to use the name "rx.y.z" as the branch name:

New Release Workflow
The steps listed in this section are to be used when creating a new release (*.0.0 or ..0) from the current main HEAD. The commands in this section assume you have named the git remote for WebOfTrust/keripy upstream.

Pull the latest main branch and ensure all tests and test scripts pass.
Update the version information in setup.py, Makefile and src/keri/init.py.
Commit your changes with git commit -a -m "New version comment".
Create the new tag for the release with git tag -a ..0 ensuring that the new tag is greater than (in semantic versioning sense) any existing tag.
Push the new tag with git push --tags upstream main.
Create and publish new PyPi package using the directions in setup.py.
Create and publish new Docker image using the Makefile
Create a new unbounded term branch for future patches name with an r the first two numbers in the version and an x as the last character using checkout -b <branch_name> tags/<tag_name>. So for the 2.3.0 release, the new branch name will be r2.3.x and the git command will be checkout -b r2.3.x tags/2.3.0.
Push the new branch to upstream

#726