Nuget Package Version and nbgv cloud NBGV_NuGetPackageVersion differ

Nerdbank.GitVersioning Version 3.1.68

version.json

{
    "$schema": "https://raw.githubusercontent.com/dotnet/Nerdbank.GitVersioning/master/src/NerdBank.GitVersioning/version.schema.json",
    "version": "0.2",
    "pathFilters": ["."],
    "publicReleaseRefSpec": [
        "^refs/heads/master$"
      ]
  }

Results in package like <Package Name>.0.2.0-g49454ca976.nupkg and NBGV_NuGetPackageVersion like 0.2.1-g49454ca976.

[saul]

Opened https://github.com/dotnet/Nerdbank.GitVersioning/pull/465 which fixes this

[saul]

OK so my understanding of the problem is that when building a project, repoRelativeProjectDirectory is the path to the directory that the csproj/fsproj lives in. When running nbgv cloud, repoRelativeProjectDirectory points to the root of the repo. This is causing version differences when relative paths are used.

I believe the bug here is that relative paths should always be relative to the version.json file, not the project directory. I’ll see if I can whip up a unit test to exercise this.