Option to increment minor or major version instead of patch
See original GitHub issueWhen the latest tag is an RTM, and is on an older commit, the patch version is incremented. E.g. if the latest tag is 1.0.0 at a height of 3 commits, the current commit version is 1.0.1-alpha.0.3.
Some projects do not use the patch version, so it would make more sense for the version to be 1.1.0-alpha.0.3. Some projects may even not use the minor version, which means the version should be 2.0.0-alpha.0.3.
This could be configurable via a new option.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:10 (9 by maintainers)
Top Results From Across the Web
Version Incrementing
When you release the next version of your library/app/website/whatever you should only increment major/minor or patch then reset all lower parts to 0, ......
Read more >Semantic Versioning 2.0.0 | Semantic Versioning
Patch and minor versions MUST be reset to 0 when major version is incremented. A pre-release version MAY be denoted by appending a...
Read more >Reason for MINOR vs PATCH rules in SemVer
MAJOR version when you make incompatible API changes,; MINOR version when you add functionality in a backwards-compatible manner, and; PATCH ...
Read more >Major.Minor.Patch. An illustrated guide to semantic…
This is where we meet Joe, in Joe's first major release. ... Now we can easily go back and release a fix, then...
Read more >Automatic Semantic Versioning on your Gradle project
Another approach is to increment the MAJOR after the MINOR version achieves, for example, the number 99. For example, you could have the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@adamralph maybe it was also a case of over engineering is underrated 😉 I patched it!
@leastprivilege FYI I just pushed 1.1.0-rc.1.