Same here, for all projects with packages referenced in a private repository, since sometime last week.

I have seen the "NU1101" error you mention months ago. The "dependency_file_not_found" error however started occurring for me as well a few days ago. #11520

I have seen the "NU1101" error you mention months ago. The "dependency_file_not_found" error however started occurring for me as well a few days ago. #11520

I also receiving the same error on my Dependabot weekly job now.

@sachin-sandhu or @SeanFeldman or @brettfo can you take a look on that, please? It starts failing from v0.296.0.

Chiming in to say we're also experiencing it. Our packages are hosted at nuget.pkg.github.com so I'm presuming this affects any projects with a custom feed.

Excerpt of our logs, if it helps

2025/02/13 11:06:45 INFO Temporarily removing `global.json` from `/home/dependabot/dependabot-updater/repo`.
2025/02/13 11:06:45 INFO Restoring `global.json` to `/home/dependabot/dependabot-updater/repo`.
2025/02/13 11:06:45 INFO Discovering build files in workspace [/home/dependabot/dependabot-updater/repo].
2025/02/13 11:06:45 INFO   No dotnet-tools.json file found.
2025/02/13 11:06:45 INFO   Discovered [global.json] file.
2025/02/13 11:06:45 INFO   Discovering projects beneath [.].
2025/02/13 11:06:46 INFO   No packages.config file found.
2025/02/13 11:06:46 INFO InstallDotnetSdks == true; retaining `global.json` contents.
2025/02/13 11:06:47 INFO InstallDotnetSdks == true; retaining `global.json` contents.
2025/02/13 11:07:03 WARN   Error determining dependencies from `/home/dependabot/dependabot-updater/repo/MyProject.Tests/MyProject.Tests.csproj`:
STDOUT:
  Determining projects to restore...
/home/dependabot/dependabot-updater/repo/MyProject.Tests/MyProject.Tests.csproj : error NU1101: Unable to find package MyPackage.Shared.Common. No packages exist with this id in source(s): nuget.org
/home/dependabot/dependabot-updater/repo/MyProject/MyProject.csproj : error NU1101: Unable to find package MyPackage.Shared.Common. No packages exist with this id in source(s): nuget.org [/home/dependabot/dependabot-updater/repo/MyProject.Tests/MyProject.Tests.csproj]
  Failed to restore /home/dependabot/dependabot-updater/repo/MyProject/MyProject.csproj (in 14.02 sec).
  Failed to restore /home/dependabot/dependabot-updater/repo/MyProject.Tests/MyProject.Tests.csproj (in 14.02 sec).


STDERR:


2025/02/13 11:07:04 INFO   No packages.config file found.
2025/02/13 11:07:04 INFO InstallDotnetSdks == true; retaining `global.json` contents.
2025/02/13 11:07:05 INFO InstallDotnetSdks == true; retaining `global.json` contents.
2025/02/13 11:07:07 WARN   Error determining dependencies from `/home/dependabot/dependabot-updater/repo/MyProject/MyProject.csproj`:
STDOUT:
  Determining projects to restore...
/home/dependabot/dependabot-updater/repo/MyProject/MyProject.csproj : error NU1101: Unable to find package MyPackage.Shared.Common. No packages exist with this id in source(s): nuget.org
  Failed to restore /home/dependabot/dependabot-updater/repo/MyProject/MyProject.csproj (in 1.04 sec).

Seems to occur at the same time as #11520

I'm also experiencing the same issue, no changes were made, but the jobs started failing

@sachin-sandhu or @SeanFeldman or @brettfo any update on that?

We're having exactly the same issue with an almost identical setup to @chris-smith-zocdoc. The issue appears to have started on the 4th of February.

Nothing has changed in our Dependabot config recently.

Can confirm this is only occurring on repositories of ours with private registries (using both private and public registries together), other repositories are fine if they use only public registries. All our repositories are Private.

This is something I've seen in some internal Microsoft logs recently, but I haven't been able to repro it locally.

Does anybody have a log file of this happening in a public repo? It appears that the NuGet tooling sometimes doesn't find or doesn't honor NuGet.Config so it falls back to the default value of nuget.org which obviously doesn't have any custom or internal packages.

The next step of the failure is that if a restore operation fails, we have no idea what packages were used by a .csproj so we don't report that file and the final step is that if no .csproj files were reproted, the job fails because nothing can be done.

This is something I've seen in some internal Microsoft logs recently, but I haven't been able to repro it locally.

Does anybody have a log file of this happening in a public repo? It appears that the NuGet tooling sometimes doesn't find or doesn't honor NuGet.Config so it falls back to the default value of nuget.org which obviously doesn't have any custom or internal packages.

The next step of the failure is that if a restore operation fails, we have no idea what packages were used by a .csproj so we don't report that file and the final step is that if no .csproj files were reproted, the job fails because nothing can be done.

Here's a very minimal reproduction using a GitHub NuGet store:

Dependabot log
Repository

Dependabot CLI works just fine, here's the log:
Dependabot CLI log

Encountering the same issue with my projects. Receiving a dependency_not_found error.

Please can you react ("👍 ") to the issue as they use that to gauge the impact

I think I found it!

I thought the casing of the file NuGet.Config was irrelevant, but it's not. The only allowed names are nuget.config, NuGet.config, and NuGet.Config, but if a repo has that file named Nuget.config or some other unapproved variant the NuGet code won't find the file and will fall back to the default value of api.nuget.org.

The reason dependabot might fail is because it runs in a Linux container with a case-sensitive filesystem and if a customer's repo is only ever built on Windows, then the file casing doesn't matter.

The fix will be to normalize all NuGet.Config file names before any update operation runs, so I'll get started on that.