Skip to content
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

Open
1 task done
xt0rted opened this issue Dec 16, 2023 · 6 comments
Open
1 task done
Labels
L: dotnet:nuget NuGet packages via nuget or dotnet T: bug 🐞 Something isn't working

Comments

@xt0rted
Copy link

xt0rted commented Dec 16, 2023

Is there an existing issue for this?

  • I have searched the existing issues

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

@azhuge233
Copy link

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.
For me, there are no errors about read-only file system though, it only has errors like

  proxy | 2023/12/28 16:22:02 [377] 400 https://dc.services.visualstudio.com:443/v2/track
  proxy | 2023/12/28 16:22:02 [377] Remote response: {"itemsReceived":1,"itemsAccepted":0,"errors":[{"index":0,"statusCode":400,"message":"103: Field 'time' on type 'Envelope' is older than the allowed min date. Expected: now - 172800000ms, Actual: now - 612414003ms"}]}

@xt0rted
Copy link
Author

xt0rted commented Dec 31, 2023

I just noticed a couple of the PRs we got at work this week are not only not updating all the packages the PR says it is, but they're also duplicating the packages in the PR description.

image

image

@jmfennell
Copy link

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.

@samtrion
Copy link

samtrion commented Jan 2, 2024

Similar / same error pattern as #8576

@pdevito3
Copy link

pdevito3 commented Jan 4, 2024

also seeing this across multiple repos

Screenshot 2024-01-04 at 1 39 13 PM

@kmcc049
Copy link

kmcc049 commented Jan 14, 2024

This is a duplicate of #8576

@brettfo brettfo moved this to Planned in Dependabot May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L: dotnet:nuget NuGet packages via nuget or dotnet T: bug 🐞 Something isn't working
Projects
Status: Planned
Development

No branches or pull requests

7 participants