feat(nuget): add version scheme

[mark-raymond]

NuGet packages sometimes use version numbers with more than 3 parts, which Renovate doesn't work with by default as they don't conform to SemVer. You can switch to the "loose" version scheme, as suggested in #4027, but that doesn't correctly differentiate between prerelease and stable packages.

This PR introduces a dedicated "nuget" version scheme, that follows closely how NuGet itself compares versions. I believe this more completely resolves #4027.

I hope that this can become the default version scheme for nuget, in lib/manager/nuget/extract.ts, but I didn't include changing the default in this PR in case that's too controversial!

[mark-raymond]

The one test failure is in code I didn't change; I guess that's spurious and needs rerunning?

[rarkins]

@mark-raymond thanks for the PR. I think let's merge it as-is for now (i.e. opt-in), then you can fully test it in production, and if after some weeks you are happy with it then we can evaluate whether to make it the default for nuget.

Perhaps also we can create a new issue to track implementing range support for NuGet versioning

[mark-raymond]

That all sounds good to me 🙂

[renovate-release]

🎉 This PR is included in version 19.66.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[nyctef]

What's the best way to use this version scheme? I've tried setting

{
  "nuget": {
    "versionScheme": "nuget"
    ...
  }
  ...
}

but that didn't seem to work - I'm still seeing "skipReason": "not-version" on some nuget packages in the job log. I could try setting versionScheme: nuget at the top level config, but that'd probably be a bad idea for us since we're also using npm and other package types in the same repo.

[mark-raymond]

Yeah, I couldn't get it to work inside the "nuget" section; I just set it at the top level because the repos I was dealing with were nuget only.

[rarkins]

Please raise a new issue in the config-help repository instead, and you can link a reference back to this issue if you like. If it turns out to be impossible or a bug, we will then treat it as a new issue back in this repository.