NuGet Updater
Open the app: Update NuGet packages → (products.documentize.ai)
In one sentence
NuGet Updater checks a GitHub repository for outdated NuGet packages and either reports them or bumps them and opens a pull request with a report of what changed and what was held back.
What makes it unique
It edits only the version values where packages are declared (central Directory.Packages.props, .csproj files, shared .props/.targets), checks each bump against the version ranges your other packages require, and reverts any bump that adds new errors. The pull request lists every update and every update it did not make, with the reason.
When to use it / when not to
- Use it for routine dependency hygiene, or to see what is behind before an upgrade sprint.
- Not for projects on
packages.config(unsupported). Versions written as MSBuild properties (such as$(MyVersion)) are reported but not changed. - To see what a new version changes in the API → Assembly Chat with Diff.
Before you start
- A GitHub repository, as
owner/nameor URL, with SDK-style .NET projects usingPackageReference. - Private repository? Invite
arise-projectas a collaborator. If it can push to the repository, the update branch is created there; otherwise the pull request is opened from its fork. The working copy is deleted when the job ends. - Optional policy: add a
nugetnews.jsonfile at the repository root to pin packages with a reason, ignore them, or allow prereleases, with wildcards likeMicrosoft.Extensions.*.
Step by step
- Enter the GitHub repository; optionally a Branch and a Solution (.sln).
- Choose the Mode, Smallest update to include, Maximum packages and Verify by.
- Run it. The page shows a report.
- In pull-request mode, open the pull request, let your CI build it, and merge.
- Download the report if you want it as a file.
Options explained
| Option | What it does | Default | Recommended |
|---|---|---|---|
| Solution (.sln) | Limit the run to one solution | all solutions | Set it in monorepos |
| Mode: Report only | Lists available updates, changes nothing | selected on the page | Start here |
| Mode: Update and open a pull request | Applies bumps on a new branch and opens a pull request | – | After reading the report |
| Mode: Watch weekly | Offered on the page but not scheduled yet; such a run only reports | – | Do not rely on it |
| Smallest update to include | Patch, Minor or Major: bumps smaller than this are skipped | Patch | Patch/Minor for safety |
| Maximum packages | Apply at most this many, smallest bump first (1 to 500) | 100 | Lower it for reviewable pull requests |
| Verify by | Automatic, Restore or Compile | Automatic | Automatic |
What you get
- A markdown report (
nuget-updates.md) and an on-page report. - In pull-request mode: one commit changing only version values (plus lock files if your restore updates them). The description lists each updated package with old and new version, plus reverted or skipped ones with reasons.
- If no build could run, the pull request is a draft marked not build-verified.
Quality & limits
Deterministic dependency work, not creative AI: versions come from nuget.org and your constraints. Verification checks dependency ranges and, where a .NET SDK is available, restores affected projects; the page says nothing was built when it opens a draft, so your CI decides. Anything other than an explicit pull-request mode only produces a report.
Works well with
- Before: Assembly Chat to check an upgrade's API changes.
- After: Repo Docs to refresh docs.
- Related: Refactor Assistant.
Common mistakes & fixes
- Expected a pull request, got a report → pick the pull-request mode.
- A package was not updated → it is pinned, ignored, outside your minimum bump, or a dependent package does not accept the new version; read the held-back list.
- Version as
$(Property)unchanged → by design; edit by hand. - Pull request is a draft → nothing was built; run your CI.
Same thing elsewhere
Not verified for this app. See channels.
Try it
Run Report only on a public .NET repository with Smallest update = Major. Count the updates, then rerun with Patch and see how the list grows. Never start with pull-request mode on a repository you do not control.