nuget-diff-analyzer — structured NuGet version-diff reports

⚡ Prefer the MCP tool. The maf-autopilot MCP server exposes MafDiffPackage(packageId, oldVersion, newVersion) — it targets the exact dotnet-inspect@0.9.1 -- diff format, parses the markdown output into a structured DiffParseResult (Breaking / Additive / NewlyObsolete lists), and cross-references each finding against the obsolete-API registry. The procedural walkthrough below is preserved for when you need to run the steps manually.

Why this exists

Raw dotnet-inspect diff output is markdown-pretty but unstructured — the LLM has to re-parse it on every call. The MCP tool does the parsing once and returns structured findings that downstream tools (best-practice reviewer, migration auditor) can consume directly.

Manual fallback workflow

# Step 1: emit the raw diff
dotnet-inspect diff \
  --package Microsoft.Agents.AI@1.2.0..1.3.0 --source https://api.nuget.org/v3/index.json

# Step 2: read the output. It has the shape:
#   # API Diff: <package>
#   | Versions | **1.2.0** -> **1.3.0** |
#   | Summary  | N breaking, M additive across K types |
#
#   ## Breaking Changes
#   ### <Type>
#   - Member '...' signature changed: `oldSig` -> `newSig`
#   - Member '...' was removed
#
#   ## Additive Changes
#   ### <Type>
#   - Type '...' was added
#   - Member '...' was added

# Step 3: for each breaking change, look up the registry:
#   MafApiSafety("<symbol-name>")
# or browse .github/skills/maf-obsolete-api-registry/registry.yaml

Output categories (what MafDiffPackage produces)

Pin reminder

Use exact dotnet-inspect 0.9.1. Versions before 0.7.8 miss [Obsolete] at the overload level — see issue #316 — and 0.9.1 avoids the redirected-output corruption encountered by the release watcher. Install it with dotnet tool install --global dotnet-inspect --version 0.9.1 before running the direct invocation above.