NuGet version update with version number having 4 segments fail #9658
Labels
L: dotnet:nuget
NuGet packages via nuget or dotnet
L: git:submodules
Git submodules
T: bug 🐞
Something isn't working
Is there an existing issue for this?
Package ecosystem
NuGet
Package manager version
Projects use the new SDK-style
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
Updated dependency
No response
What you expected to see, versus what you actually saw
We have lots of internal NuGet packages in a private feed that still use the older version number syntax that have 4 segments. When enabling dependabot version updates it fails to run with above error because it can't parse the version number as a semantic version.
I expect dependabot to work also with NuGet versions that have 4 digit groups.
I took a check in the code and next to the SemanticVersionFactory in the stack trace I found this NuGetVersion class that appears to handle it
I also found this page that mentions NuGet versioning being different from Semantic Versioning
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
Smallest manifest that reproduces the issue
If you believe it to be useful I can try to find a public NuGet package and create a small public repository that reproduces this issue.
The text was updated successfully, but these errors were encountered: