Add Renovate config for .NET package grouping

[tamararivera]

Added configuration for .NET packages in Renovate.

[tamararivera]

I reviewed all the open and recently closed Renovate PRs for packages that start with System and I have nothing to add other than what David already mentioned.
I found only dependencies that we don't use anymore or that are released with .NET (System.CommandLine).

Oh, and I added the rule for System.Private.**, but that is only used on samples and snippets 🤷‍♀️

[bording]

I reviewed all the open and recently closed Renovate PRs for packages that start with System and I have nothing to add other than what David already mentioned. I found only dependencies that we don't use anymore or that are released with .NET (System.CommandLine).

Oh, and I added the rule for System.Private.**, but that is only used on samples and snippets 🤷‍♀️

What examples do you have for needing those other exemptions? From doing a quick look at the packages they would cover, I'm not sure those are really relevant in that they seem to be old packages that aren't actually released anymore.

[tamararivera]

If we discard all the usages from samples, snippets and some random non product repos, I see:

• System.Data, referenced by ServiceInsight and tests for DocsEngine: https://github.com/search?q=org%3AParticular+System.Data+language%3AXML++NOT+is%3Aarchived&type=code&l=XML
• System.Private, referenced by the EndpointThroughputCounter https://github.com/search?q=org%3AParticular+System.Private+language%3AXML++NOT+is%3Aarchived&type=code
• System.Net, referenced by smoke tests on ServicePulse

I decided to add them, just in case a new version for them happens to appear, as I don't want that to be bundled with the real .NET packages

[mauroservienti]

Is there any risk in getting all those bundled in all repos?

[bording]

If we discard all the usages from samples, snippets and some random non product repos, I see:

• System.Data, referenced by ServiceInsight and tests for DocsEngine: https://github.com/search?q=org%3AParticular+System.Data+language%3AXML++NOT+is%3Aarchived&type=code&l=XML
• System.Private, referenced by the EndpointThroughputCounter https://github.com/search?q=org%3AParticular+System.Private+language%3AXML++NOT+is%3Aarchived&type=code
• System.Net, referenced by smoke tests on ServicePulse

I decided to add them, just in case a new version for them happens to appear, as I don't want that to be bundled with the real .NET packages

@tamararivera None of those will ever be updated, they are all legacy things from a different .NET Core era that aren't being produced anymore. I think it's safe to not worry about listing exceptions for them.

Is there any risk in getting all those bundled in all repos?

@mauroservienti IMO it's not really about risk. The reason to bundle some but not others is tied to how the packages are versioned and shipped. The System.* and Extensions package all maintain the same versions and are released at the same time. You "should" be referencing the same version of all of those packages when you use them, to it makes sense to raise a single PR when they are released.

The others have a different release cadence and versioning, so I want to see those in separate PRs with a clear title, and not just another ".NET Packages" update PR.

EDIT: So, I guess the risk is that it seems fine to bundle things that are already related and ship in lockstep, but adding things that have their own release cadence you miss reviewing them as their own separate thing.

[tamararivera]

Okay, you have convinced me 😅, I have updated the list, in case that we ever need to change the list, now we all know were it is 😛