You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realize that this isn't supported by all package managers, but there are some use cases (patching a port) where it makes sense to have a 4-th version component, as well as the ability to have 4 component version numbers with a prerelease label.
Of course, this should be a non-default option. It isn't clear what to do for NPM version, but I would suggest either leaving it as a 3-component number or throwing an exception when this option is enabled.
This article demonstrates that the major.minor.build.revision[-prerelease] is a legacy format that historically has been supported by NuGet.
The change should update both FileVersion and AssemblyInformationalVersion to use 4 segments as well as NuGetPackageVersion.
For our temporary workaround for this feature, we ended up reworking the logic for forcing non-zero version numbers to automatically "bump" it to 4 components, but only if 4 components are provided. Otherwise, it will be 3 components.
The differences in comparison logic and defaulting are a bit subtle from the way NerdBank.GitVersioning currently does it, but this is what ultimately works to allow 4 components without requiring 4 components.
From the discussion in #708.
I realize that this isn't supported by all package managers, but there are some use cases (patching a port) where it makes sense to have a 4-th version component, as well as the ability to have 4 component version numbers with a prerelease label.
Of course, this should be a non-default option. It isn't clear what to do for NPM version, but I would suggest either leaving it as a 3-component number or throwing an exception when this option is enabled.
This article demonstrates that the
major.minor.build.revision[-prerelease]
is a legacy format that historically has been supported by NuGet.The change should update both
FileVersion
andAssemblyInformationalVersion
to use 4 segments as well asNuGetPackageVersion
.The text was updated successfully, but these errors were encountered: