PR for fundamental re-structuring of the current implementation
Move to Kotlin
Change approach of version calculation
Previously I have attached to the tags list, which is not ordered correctly. For example tag list:
... 0.0.8, 0.0.9, 0.0.10, 0.0.11
will be sorted by default as 0.0.11 0.0.10 0.0.8 0.0.9, which is alphabetical order and regarding this order 0.0.9 will be the latest one, which is incorrect and doesn't allow you to have automatically generated version with the main suffix more than 9.
That behavior has been changed by correct sorting of the tags: now latest commit date for each tag is used as a tag date, which allows to determine the latest one even in the situation when you have multiple commits tagged by one tag.
Also this PR contains fixes to the following issues:
PR for fundamental re-structuring of the current implementation
Move to Kotlin
Change approach of version calculation
Previously I have attached to the tags list, which is not ordered correctly. For example tag list:
will be sorted by default as
0.0.11 0.0.10 0.0.8 0.0.9
, which is alphabetical order and regarding this order 0.0.9 will be the latest one, which is incorrect and doesn't allow you to have automatically generated version with the main suffix more than 9.That behavior has been changed by correct sorting of the tags: now latest commit date for each tag is used as a tag date, which allows to determine the latest one even in the situation when you have multiple commits tagged by one tag.
Also this PR contains fixes to the following issues:
To be done: