Skip to content

[dev-v5] Document workaround for NuGet restore errors NU3018/NU3027 #4437

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dvoituron merged 1 commit into from
Jan 5, 2026
Merged

[dev-v5] Document workaround for NuGet restore errors NU3018/NU3027 #4437

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/using-latest-daily.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,18 @@ or else in the global NuGet.config. See [configuring NuGet behavior](https://lea
Alternatively, if you are using Visual Studio, you can [Install and manage packages in Visual Studio](https://learn.microsoft.com/nuget/consume-packages/install-use-packages-visual-studio#package-sources)
and add the feed `https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json` there.

## Restore error

If you get the error **NU3018** `The author primary signature's signing certificate is not trusted by the trust provider`
or **NU3027** `The signature should be timestamped to enable long-term signature validity after the certificate has expired`,
you can work around it by adding the following to your project file:

```xml
<PropertyGroup>
<NoWarn>NU3018;NU3027</NoWarn>
</PropertyGroup>
```

## NuGet’s Central Package Management (CPM)

If you are using the NuGet’s Central Package Management (CPM) feature, you probably need to set `ManagePackageVersionsCentrally=false`
Expand Down
Loading