PR:🚇 Add deployment pipeline step

[s-weigand]

@dalthviz Thanks for the new release 🎉

Hope this makes releasing new versions easier in the future

[codecov-commenter]

Codecov Report

Merging #65 (f86f462) into master (e8e15e7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #65   +/-   ##
=======================================
  Coverage   87.52%   87.52%           
=======================================
  Files          12       12           
  Lines         513      513           
=======================================
  Hits          449      449           
  Misses         64       64           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[dalthviz]

Hi @s-weigand thank you for the help checking ways to automate a little bit the release process!

Checking the workflow changes I guess this depends on a pypi_password (PyPI token) being defined in the repository secrets, right?

Also, I think we need to update https://github.com/spyder-ide/qtsass/blob/master/RELEASE.md to follow up the changes proposed here (at least removing the duplicated steps that now should be done with Github Actions and adding a note about what happens when the git push --tags is done, i.e it is the trigger for this new deploy job).

Also, do you think it could be worthy to add some validation step to the generated distributions, like the check you can do with twine check dist/*?

Edit: Thinking a little bit more, should we instead of using the tag as trigger for this new step use the release event (so creating a GitHub release)? What do you think?

[s-weigand]

@dalthviz Yes you need to create a token at PyPI (best would be with project scope) and set the pypi_password secret of the repository to this value.

I updated the release instructions in f86f462 to match the new workflow.

The twine check dist/* is run by default in pypa/gh-action-pypi-publish so I don't think we need to duplicate it.

If you create a release you have to either use an existing tag or create a new one so the tag event will be triggered in any case.

[dalthviz]

Thanks @s-weigand !