You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What you expected to see, versus what you actually saw
If a NuGet package is pulled in via an MSBuild SDK, then dependabot will attempt to update NuGet packages associated with it (which are not referenced in any project files), fail, and then cause the dependabot job to fail.
Is there an existing issue for this?
Package ecosystem
NuGet
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
https://github.com/martincostello/alexa-london-travel/blob/main/global.json
dependabot.yml content
https://github.com/martincostello/alexa-london-travel/blob/main/.github/dependabot.yml
Updated dependency
No response
What you expected to see, versus what you actually saw
If a NuGet package is pulled in via an MSBuild SDK, then dependabot will attempt to update NuGet packages associated with it (which are not referenced in any project files), fail, and then cause the dependabot job to fail.
For example,
MSTest.Sdk
.Dependabot should not error when it encounters such dependencies and just ignore them.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: