Upgrading from 3.5.119 to 3.6.132 breaks commit id for NPM

[woppa684]

version.json

{
  "$schema":  "https://raw.githubusercontent.com/AArnott/Nerdbank.GitVersioning/master/src/NerdBank.GitVersioning/version.schema.json",
  "version":  "7.1.0-next.{height}",
  "publicReleaseRefSpec":  [
    "^refs/heads/releases/v\\d+\\.\\d+$"
  ]
}

Output of get-version for 3.5.119

Version:                      7.1.0
AssemblyVersion:              7.1.0.0
AssemblyInformationalVersion: 7.1.0-next.16+38d39d2671
NuGetPackageVersion:          7.1.0-next.16.g38d39d2671
NpmPackageVersion:            7.1.0-next.16.g38d39d2671

Output of get-version for 3.6.132

Version:                      7.1.0
AssemblyVersion:              7.1.0.0
AssemblyInformationalVersion: 7.1.0-next.16+38d39d2671
NuGetPackageVersion:          7.1.0-next.16.g38d39d2671
NpmPackageVersion:            7.1.0-next.16

Is this related to this commit? 5e1adb5

So, we use this to make distinct prereleases, should we switch to using the NuGetPackageVersion instead?

[AArnott]

I was wondering myself today if perhaps I had been mistaken in the belief behind that commit that NPM doesn't support the .commitID syntax in the version. It sounds like you agree that was a mistake. I wonder what led me to believe it was being dropped. I'll bring it back.

[woppa684]

Thanks for the quick repsonse! As far as I know, NPM just follows the semver spec, and any dot-separated prerelease identifiers after a hyphen are ok Now we'll just wait for a release :)

[woppa684]

@AArnott Any idea when a new release will be made? We have more and more repositories that need to revert now ...

[AArnott]

3.6.133 going out to nuget right now.