-
Notifications
You must be signed in to change notification settings - Fork 1k
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.
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
NuGet packages being reported as updated despite not existing in the commit #8631
Comments
The same thing started to happen in my private repo since last week, which has group update configured. It only updates one dependency in each group.
|
We are also experiencing this (in a private repo). For us, the PR description is correct (no duplicates), but it only actually bumps the version of the last dependency listed. |
Similar / same error pattern as #8576 |
This is a duplicate of #8576 |
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
Here's more in a different repo
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
There should have been 4 packages updated in the first PR, and 5 in the second, which the title & body of the PR says, but there's only 1 package updated in each. The same is true in other repos, both public and private. It seems to be any nuget update group with more than 1 package update results in only 1 package being updated while the title & body have the correct information.
I have dependabot logs in all my repos that have a TON of errors about being run on a read-only file system but I'm not sure if that's related to this issue. Both things seem to only be happening for nuget packages though.
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: