ln-712-nuget-upgrader

Overview

Workflow

Phase 0: Pre-flight Checks

Workers assume coordinator (ln-710) already verified git state and created backup.

Phase 1: Find Projects

Discovery Methods

Get-ChildItem -Recurse -Filter *.csproj

dotnet sln list

Phase 2: Security Audit

Commands

dotnet list package --vulnerable

dotnet list package --outdated

Actions

Phase 3: Check Outdated

Using dotnet-outdated

dotnet tool install --global dotnet-outdated-tool

dotnet outdated --output json

Phase 4: Identify Breaking Changes

Detection

1. Compare current vs latest major versions
2. Check breaking_changes_patterns.md
3. Use MCP tools (see below) for migration guides

Common Breaking Changes

MCP Tools for Migration Search

Priority Order (Fallback Strategy)

Context7 Usage

MCP Ref Usage

WebSearch Fallback

• "<package> .NET <version> breaking changes migration"

• "<error code> <package> fix"

Phase 5: Apply Upgrades

Priority Order

Commands

dotnet add package <name> --version <ver>

dotnet outdated --upgrade

Phase 6: Restore & Build

Commands

dotnet restore

dotnet build --configuration Release

dotnet test

On Failure

1. Identify failing package from error
2. Search Context7/Ref for migration guide
3. If unresolved: rollback package, continue

Phase 7: Report Results

Report Schema

Configuration

Options:
  # Upgrade scope
  upgradeType: major          # major | minor | patch

  # Security
  auditLevel: high
  minimumReleaseAge: 14

  # .NET specific
  includePrerelease: false
  targetFramework: net10.0

  # Verification
  runTests: true
  runBuild: true

Error Handling

References

• breaking_changes_patterns.md
• dotnet_version_matrix.md