Automate release process

[sdispater]

Pull Request Check List

• Added tests for changed code.
• Updated documentation for changed code.

This PR adds the automation of Poetry releases so that any maintainer can make a release without my intervention.

This workflow is triggered whenever a release tag is pushed. In detail, it does the following:

• Build the custom releases, those needed for the official Poetry installer, for each OS
• Create a new Github release with the tag name
• Upload the custom releases as assets of the Github release
• Upload both the source distribution file and the wheel file to PyPI

Note that it should work but will be properly tested for the next release since it's not possible to test it directly from the PR.

[justinmayer]

I love the idea of automating releases, particularly when that occurs upon pull request merge. So much so that I wrote AutoPub to accomplish exactly that. You can read more about the motivation here: https://justinmayer.com/projects/autopub/

Given that Poetry already uses GitHub Actions for CI functionality, it would be trivial to add the same auto-publication feature to this project as well. Here's an example of GitHub CI configuration that publishes to PyPI upon PR merge: https://github.com/pelican-plugins/simple-footnotes/blob/master/.github/workflows/main.yml

Just thought I'd mention this in case it's useful. Cheers!

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.