Automated release workflow based on semantic commits

[nitrocode]

what

The module could follow a semantic versioning scheme major.minor.patch

Using semantic commits, such as

• feat! for breaking backwards compatibility would cause a major version bump
• feat for a new feature with backwards compatibility would cause a minor version bump
• fix would be a bugfix that would cause a patch version bump

all others like chore or ci or docs would not result in a new release

why

This can help keep releases separated and easy to downgrade or upgrade to new versions

references

• Here is an example https://medium.com/zencore/managing-terraform-modules-with-github-actions-9702a78fe988
• https://www.conventionalcommits.org/en/v1.0.0/

[paulschwarzenberger]

Sounds good to me!