Proposal to Automate Package Publishing with GitHub Actions and Git Versioning

[FlavioAmurrioCS]

This is something I am more than happy contributing you are open to the idea :)

I am more or less going follow the same approach I did here but adapt it to poetry rather then hatch.
https://github.com/FlavioAmurrioCS/workflows/blob/main/.github/workflows/common-python.yml
https://github.com/FlavioAmurrioCS/workflows/blob/main/.github/workflows/main.yml

Release notes would also automatically get generated.
example: https://github.com/FlavioAmurrioCS/persistent-cache-decorator/releases

I would like to propose an enhancement to facilitate publishing package distribution releases. This enhancement involves the use of GitHub Actions to automate the build and publishing process, as well as the adoption of Git versioning for managing release versions.

Automate Publishing with GitHub Actions

By integrating GitHub Actions, we can streamline our release process and ensure consistency in our package distributions. GitHub Actions allows us to set up Continuous Integration and Continuous Deployment (CI/CD) workflows that can automate the build and publishing steps.

Here is a guide that outlines the process of publishing package distribution releases using GitHub Actions: Publishing Package Distribution Releases using GitHub Actions.

Use Git Versioning

To further simplify our release process, I propose that we adopt Git versioning. With this approach, all we would need to do is tag a commit with a version identifier (e.g., v1.4.2). Once tagged, the GitHub Action workflow will automatically run the necessary steps to build and publish the package.