Config CD to respect conventional commits
Closed this issue · 2 comments
Is your feature request related to a problem? Please describe.
All changes merged on master generate a new version of packages and in some cases, this shouldn't happen.
Changes that do not affect the API must not be deployed (examples: changes on non-source files). This brings minimal versions, changelog, and costumers package updates.
Describe the solution you'd like
As we have already used conventionalcommits pattern we can determine through the commit message what change this commit represents. If that change represents a major, minor, or patch we can generate and deploy a new version following the semver specification.
Describe alternatives you've considered
- https://dwmkerr.com/conventional-commits-and-semantic-versioning-for-java/
- https://github.com/KengoTODA/gradle-semantic-release-plugin
- https://blog.usejournal.com/semantic-release-for-fastlane-781df4cf5888
- https://www.thoughtworks.com/en-br/insights/blog/automating-semantic-versioning-model-mobile-releases
This could bring us automatic changelog and github releases 🚀
Atualmente estamos utilizando o convention commits