Sergei Zharinov

We need to port relevant tests from Nuget: - [x] [FloatingRangeTests.cs](https://github.com/NuGet/NuGet.Client/blob/dev/test/NuGet.Core.Tests/NuGet.Versioning.Test/FloatingRangeTests.cs) - [x] [NuGetVersionTest.cs](https://github.com/NuGet/NuGet.Client/blob/dev/test/NuGet.Core.Tests/NuGet.Versioning.Test/NuGetVersionTest.cs) - [ ] [SemVer201SpecTests.cs](https://github.com/NuGet/NuGet.Client/blob/dev/test/NuGet.Core.Tests/NuGet.Versioning.Test/SemVer201SpecTests.cs) - [ ] [SemanticVersionConverterTests.cs](https://github.com/NuGet/NuGet.Client/blob/dev/test/NuGet.Core.Tests/NuGet.Versioning.Test/SemanticVersionConverterTests.cs) - [ ] [SemanticVersionTests.cs](https://github.com/NuGet/NuGet.Client/blob/dev/test/NuGet.Core.Tests/NuGet.Versioning.Test/SemanticVersionTests.cs) - [ ] [VersionComparerTests.cs](https://github.com/NuGet/NuGet.Client/blob/dev/test/NuGet.Core.Tests/NuGet.Versioning.Test/VersionComparerTests.cs)...

Don't close, I'll continue

There is a tool for verification: https://nugettools.azurewebsites.net/6.11.0-preview.2/parse-version?version=1.2.3.4.5

- Do we still need it after #25666?

As an option, `RENOVATE_X_`

Thanks for pointing out, I didn't know about this issue. No, I think it's orthogonal to it, and by the way we returned back the older coverage policy, as the...

What's the benefit of minimatch usage, given it's being used mostly for filesystem patterns? Maybe, instead we want to just match regex once the pattern is `/.../`, falling back to...

I used this config: ```json { "logLevelRemap": [ { "matchMessage": "cache", "newLogLevel": "info" } ] } ``` It's not intuitive that I actually needed to use `*cache*` 🤷‍♂️

Well, I think per-repo

> We should do this using our existing or an enhancement of our log "factory". Additionally, when we use log levels for application level logic (e.g. putting warnings in the...