Skip to content

NuGet

Renovate can upgrade dependencies in these files:

  • .csproj
  • .fsproj
  • .vbproj

Version Support

Renovate only works with SDK-style .csproj, .fsproj or .vbproj files. By default, this includes:

  • .NET Core 1.0 and above
  • .NET Standard class libraries
  • .csproj, .fsproj or .vbproj files that use the SDK-style syntax

To convert your .NET Framework .csproj, .fsproj or .vbproj files into an SDK-style project, follow the steps in this guide.

How it works

  1. Renovate searches in each repository for any files with a .csproj, .fsproj, or .vbproj extension
  2. Existing dependencies are extracted from <PackageReference> and <PackageVersion> tags
  3. Renovate looks up the latest version on nuget.org (or an alternative feed if configured) to see if any upgrades are available
  4. If the source package includes a GitHub URL as its source, and has either:

  5. a "changelog" file, or

  6. uses GitHub releases

then release notes for each version are embedded in the generated PR

If your project file references a packages.config file, no dependencies will be extracted. Find out here how to migrate from packages.config to PackageReference.

Alternate feeds

By default Renovate performs all lookups on https://api.nuget.org/v3/index.json, but you can set alternative NuGet feeds. You can set alternative feeds:

  • in a NuGet.config file within your repository (Renovate will not search outside the repository), or
  • in a Renovate configuration options file like renovate.json
{
  "nuget": {
    "registryUrls": [
      "https://api.nuget.org/v3/index.json",
      "https://example1.com/nuget/",
      "https://example2.com/nuget/v3/index.json"
    ]
  }
}

In the example above we've set three NuGet feeds. The package resolving process uses the merge strategy to handle the three feeds. All feeds are checked for dependency updates, and duplicate updates are merged into a single dependency update.

Warning

If your project has lockfile(s), for example a package.lock.json file, then you must set alternate feed settings in the NuGet.config file only. registryUrls set in other files are not passed to the NuGet commands.

Protocol versions

NuGet supports two protocol versions, v2 and v3. The NuGet client and server must use the same version. When Renovate acts as the client, it can use the v2 and v3 protocols.

By default, Renovate uses the v2 protocol. If the configured feed URL ends with index.json, Renovate uses the v3 protocol. So Renovate behaves like the official NuGet client.

v3 feed URL not ending with index.json

If a v3 feed URL does not end with index.json, you must append #protocolVersion=3 to the registry URL:

{
  "nuget": {
    "registryUrls": ["http://myV3feed#protocolVersion=3"]
  }
}

You may need this workaround when you use the JFrog Artifactory.

Authenticated feeds

Credentials for authenticated/private feeds can be given via host rules in the configuration options (file or command line parameter).

{
  "hostRules": [
    {
      "hostType": "nuget",
      "matchHost": "http://example1.com/nuget",
      "username": "root",
      "password": "p4$$w0rd"
    }
  ]
}

If you're using Azure DevOps, you can set matchHost to pkgs.dev.azure.com.

Note

Only Basic HTTP authentication (via username and password) is supported. For Azure DevOps, you can use a PAT with read permissions on Packaging plus an empty username. The generated nuget.config enforces basic authentication and cannot be overridden externally!

Future work

We welcome contributions or feature requests to support more patterns or use cases.