Source: itnext.io
I made Semantic Versioning easyCategory: github, yaml
emantic versioning of your software — wherever we are talking about microservices or monolith applications can put a serious strain on the relationship at work. As ridiculous as it may sound — the theory of patch, minor, and finally major versions is easy.
Something that, for one person, is a minor could be considered just a patch by the other person, taking away the joy of being the new release participant and directly influencing the mood and will to contribute within the project.
It allows you to define sets of keywords on which specific part of the version will be incremented.
To maintain the appropriate order, you can use the following as a part of your config file: And next produced version will be 1.5.9 as the commit 97d368 counts as one.
Something that, for one person, is a minor could be considered just a patch by the other person, taking away the joy of being the new release participant and directly influencing the mood and will to contribute within the project.
It allows you to define sets of keywords on which specific part of the version will be incremented.
To maintain the appropriate order, you can use the following as a part of your config file: And next produced version will be 1.5.9 as the commit 97d368 counts as one.
Related Articles
Community Partners
DevOps Careers