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
# Please see the documentation for all configuration options:# https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-fileversion: 2updates:
- package-ecosystem: nugetdirectory: /schedule:
interval: weeklyignore:
- dependency-name: Newtonsoft.Json # This has to match VS and VS rarely updates it
- dependency-name: Microsoft.AspNetCore.TestHost # Later versions require .NET Core 3.1, which prevents our testing on net472# We want to match the minimum target .NET runtime
- dependency-name: System.Threading.Tasks.Dataflow
- dependency-name: System.Collections.Immutable
- dependency-name: System.Diagnostics.DiagnosticSource
- dependency-name: System.Text.Json
Notice how it again calls out Microsoft.Bcl.AsyncInterfaces as updated when in fact it is untouched. Notice further how it claims to "update" from 8.0.0down to 6.0.0. Why in the world would it believe that?
Native package manager behavior
It would have just updated xunit.combinatorial 2.0.24.
This would by the way cause build breaks, because this major update of this package brings in a whole new tree of dependencies including xunit.v3 which will provide colliding types to the compiler. But this isn't something I expect Dependabot to be able to predict and manage.
Images of the diff or a link to the PR, issue, or logs
AArnott
changed the title
Version update PRs created with incorrect claims in title and description about what's being updated
Version update PRs overstate what's being updated in title and description
Jan 21, 2025
Is there an existing issue for this?
Package ecosystem
nuget
Package manager version
No response
Language version
MSBuild
Manifest location and content before the Dependabot update
/Directory.Packages.props
dependabot.yml content
Updated dependency
What you expected to see, versus what you actually saw
The PR title was: "Bump Microsoft.Bcl.AsyncInterfaces and xunit.combinatorial" yet only xunit.combinatorial was updated.
The PR description was:
Notice how it again calls out Microsoft.Bcl.AsyncInterfaces as updated when in fact it is untouched. Notice further how it claims to "update" from 8.0.0 down to 6.0.0. Why in the world would it believe that?
Native package manager behavior
It would have just updated xunit.combinatorial 2.0.24.
This would by the way cause build breaks, because this major update of this package brings in a whole new tree of dependencies including xunit.v3 which will provide colliding types to the compiler. But this isn't something I expect Dependabot to be able to predict and manage.
Images of the diff or a link to the PR, issue, or logs
microsoft/vs-streamjsonrpc#1116
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: