Currently, version number in our GA release are inputed by hand. This is prone to mistakes if we incremented minor version but after the release pipelines run we discover that it should have been major increment because of a feature PR. During a release Github Action (GA) invocation we are setting built release version as an input parameter. This parameter is then validated with pull requests (PR) included in this release and a previous release version. If the release contains a pr with kind/feature label then the minor part of the version number needs to be incremented in comparison to the previous release version. Otherwise, only a patch version is allowed to be changed. This behaviour can be changed to introduce automatic version increments based on PRs from the release.
AC
[ ] remove version input parameter from our release GA,
[ ] add release steps that populate the parameter internally,
[ ] calculate the release version based on previous version,
[ ] increment the previous release - if the release contains kind/feature pr then increment minor number,
[ ] if the release does not contain kind/feature then increment patch part of the number.
Currently, version number in our GA release are inputed by hand. This is prone to mistakes if we incremented minor version but after the release pipelines run we discover that it should have been major increment because of a feature PR. During a release Github Action (GA) invocation we are setting built release version as an input parameter. This parameter is then validated with pull requests (PR) included in this release and a previous release version. If the release contains a pr with
kind/featurelabel then the minor part of the version number needs to be incremented in comparison to the previous release version. Otherwise, only a patch version is allowed to be changed. This behaviour can be changed to introduce automatic version increments based on PRs from the release.AC
kind/featurepr then increment minor number,kind/featurethen increment patch part of the number.