publish new volttron wheel to pypi

[craig8]

Start publishing dev versions of volttron wheel to pypi when a pr is merged to develop.

Publish new version "released" of wheel to pypi when a merge to releases is done.

@shwethanidd @bonicim @jhaack @schandrika When should the incrementation of the version number be done do you think? In the github actions?

[craig8]

https://www.python.org/dev/peps/pep-0440/

[craig8]

I believe we should use this workflow https://aboutbits.it/blog/2021-03-11-using-github-actions-to-perfom-npm-version-increment.

as a pattern perhaps...

Two things we would change are:

• we are using poetry so we would use poetry version minor
• we would make the changes based upon the branch not on the commit message.

Thoughts?

[craig8]

So our incrementation is going to be based upon releases of dev versions and the workflow will be as follows.

1. Merge/commit to develop.
2. Check the commit message for [RELEASE] if not found then increase version number of patch with dev and commit it to the repository.
3. Deploy the pyproject if [RELEASE] is found in the head message.

[craig8]

After using this in a test repo https://github.com/craig8/test-release-actions/tree/develop

I don't like the "RELEASE" thingy being pushed back to the repo. Everyone would have to rebase/merge after each commit. So instead I think we tag a release and push the artifact when a push to develop happens.

Much cleaner.

[bonicim]

I like how we auto-increment the version number instead of manually having to set the version number ourselves. Doing it within Github Actions and using Poetry to increment makes sense.