build: name Nerdbank.GitVersioning in the packable project so Publish.ps1 finds it

[rolandbanks]

Summary

Publish.ps1 cannot publish this package. It fails before it gets as far as NuGet:

Could not find a packable project referencing Nerdbank.GitVersioning.

The script locates the project to read the version from by scanning *.csproj for the literal text Nerdbank.GitVersioning. This repository declares it once in Directory.Build.props — which applies it to every project, but leaves it absent from every .csproj, so the scan matches nothing.

The fix

One line: a PackageReference Update item naming the package at project level, which is what MicrosoftDynamics.Api already does.

Update rather than Include, so the version stays governed centrally by Directory.Packages.props and nothing about the build changes — it is a metadata no-op that restores the project-level mention the script looks for.

Fixed this way rather than by changing the detection logic, so Publish.ps1 stays byte-identical across the repositories that share it.

Scope

Only two repositories were affected — the only two declaring the versioning package solely in Directory.Build.props. The other was MicrosoftAzure.Api, fixed under b4f4c21 earlier today. I swept the rest and found no others.

Verification

Ran the script's own detection and version steps directly, without pushing a tag:

Detected: PanoramicData.OData.Client.csproj
ExitCode: 0
Version would be: 10.0.121-gaae7e87b87

(The -g<sha> suffix is only because this ran on a branch; on main it resolves to a clean 10.0.121.)

dotnet build -c Release — 0 errors, 0 warnings, and the 36 header-redaction tests still pass.

🤖 Generated with Claude Code

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}