When to use / when NOT to use
- •Use for NuGet hygiene and controlled upgrade planning/execution.
- •Do not use for SDK pinning changes (use
dotnet-sdk-align).
Preconditions (tools, versions, repo state)
- •
dotnetCLI installed. - •Repo has .NET projects and optional central package management files.
Workflow (DISCOVER → PLAN → EXECUTE → VERIFY → REPORT)
- •DISCOVER: locate version-definition files (
Directory.Packages.props,*.csproj, lockfiles). - •PLAN: define package bump slices based on outdated output.
- •EXECUTE: restore and generate upgrade candidates (manual targeted bump step).
- •VERIFY: restore/build/test + outdated re-check.
- •REPORT: summarize safe next edits for review.
Exact commands and expected signals
bash
skills/dotnet-packages-upgrade/scripts/run.sh --dry-run skills/dotnet-packages-upgrade/scripts/run.sh --execute --ci skills/dotnet-packages-upgrade/scripts/run.sh --verify-only --ci
Success: outdated inventory and verification output produced.
Failure: missing dotnet or build/test failures after upgrades.
If it fails (checklist)
- •Confirm SDK/runtime compatibility.
- •Run restore with detailed logs.
- •Verify central package versions are coherent.
Final report template
- •Version-definition locations discovered.
- •Outdated package summary.
- •Restore/build/test/analyze outcomes.
- •Recommended package bump PR chunks.
- •Rollback command.