Allow a fourth "Revision" version part to be used.
Juff-Ma opened this issue · 3 comments
Use case(s)
- allows to create a version with no significant changes and bugfixes to create a version for a different kind of change. For example update a packages readme or help.
- allows a package thats dependent on another library to use the 3-part version of the dependency to be the main part of the version while still having a part of itself for versioning (for example native bindings)
- conforming with the nuget version spec that explicitely requires this (Where NuGetVersion diverges from Semantic Versioning)
Description
Allow a fourth "Revision" version part to be used with MinVer. So that w.x.y.z is possible to use with MinVer. If this is already possible it isn't in the documentation.
Alternatives
- Let MinVer only update the first 3 parts and add the fourth one manually (kinda defeats the point of MinVer)
- create a completely new Patch version even if there wasn't really a bugfix
- create a whole new version system for bindings and only state compatible versions (would make it harder to get such information only from the Version number)
- for bindings define the major version of the library manually and let MinVer only define the second, third and fourth part. (would be kinda confusing, for example when library version 2.4.3.2 and 3.4.3.2 exist)
Additional context
The Nuget packaging version Spec, as well as the assembly version (and i guess also the FileVersion) all support a fourth "Revision" part, however none of the major git versioning tools seem to support it.
@Juff-Ma this is not a use case I have but I'd be happy to accept a PR if the change doesn't add significant complexity. If you would like to spike the implementation I'd be happy to take a look, but I can't guarantee I'll accept a PR.
If you have budget available and are interested in engaging my professional services to get this done, please feel free to contact me at adam@adamralph.com and we can discuss details.
@adamralph As this also isn't a top priority for me i wouldn't want to pay someone to do it. However after a quick look it seems the only major change that would need to happen is to change from NuGets SemanticVersion to NuGetVersion.
I'll try to look into it myself and try to change all the references