Bump version and document release process

[allisonnicoledeal]

Wanted to release a new updated with the new cancel_event method, which is needed for deleting input devices on the Propeller side.

I don't know what I'm doing here as far as the release goes, but wanted to start documenting..what else is needed?

Fixes https://github.com/cbsinteractive/propeller/issues/1529

[codecov]

Codecov Report

Merging #71 into master will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #71      +/-   ##
==========================================
+ Coverage   99.25%   99.29%   +0.03%     
==========================================
  Files           2        2              
  Lines         134      141       +7     
  Branches        8        8              
==========================================
+ Hits          133      140       +7     
  Partials        1        1              

Impacted Files	Coverage Δ
elemental/client.py	99.28% <0.00%> (+0.03%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1616157...9d5b8ba. Read the comment docs.

[igorsobreira]

@allisonnicoledeal I believe we need to build first:

poetry build
poetry publish

or

poetry publish --build

https://python-poetry.org/docs/cli/#publish

[igorsobreira]

@allisonnicoledeal just realized we have a makefile, here is an idea:

release: clean-build
    poetry publish --build

I haven't tried yet 🙂

[rafaelcaricio]

That is basically it. Later we can create a user in PyPI just for publishing releases and create a Github workflow to do it automatically based on tags. #74

[allisonnicoledeal]

@allisonnicoledeal just realized we have a makefile, here is an idea:

release: clean-build
    poetry publish --build

I haven't tried yet 🙂

Success! 9d5b8ba