COMMON: Automate semantic version determination
khauser opened this issue · 0 comments
Based on commit messages it's possible to determine if a change to a chart is major, minor or patch. The main person who should know which version to bump is the developer. So he could mark his feature-commit (features should be squashed) with the needed information.
How to use semantic versioning to determine the version increment, e.g.: https://python-semantic-release.readthedocs.io/en/latest/commit-parsing.html
At the moment we use this action to build a release branch from a develop branch. With an input like "icm-as:minor" the action could be started. But this input could be also gained from the information whitin the commit messages of the branch differences. E.g. one commit message contains "BREAKING CHANGE" and addresses a file in the icm chart then "icm:major" should be used for the release process.