Package validation Baseline Package Validator should optionally check semantic versioning rules

When enabling Package Validation against a baseline version like this:

<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>net6.0</TargetFramework> <PackageVersion>1.0.1</PackageVersion> <EnablePackageValidation>true</EnablePackageValidation> <PackageValidationBaselineVersion>1.0.0</PackageValidationBaselineVersion> </PropertyGroup> </Project>

Validation should not only report breaking changes but (optionally) say if the new package complies to semantic versioning rules. E.g.:

• If there are breaking changes it should recommend that major version has to be incremented.
• If there are non breaking changes it should recommend that minor version has to be incremented.

[ViktorHofer]

That sounds like a good feature request for https://github.com/pushpay-labs/semantic-versioning-analyzer. What you are asking for is achievable by adding an msbuild task and making sure that it runs after the Pack target. In your project you would then just need to add a PackageReference to that msbuild task and optionally set a few properties to control its behavior:

<ItemGroup>
    <PackageReference Include="SemVerAnalyzer.Task" Version="..." />
</ItemGroup>

Such a solution would work with Visual Studio as well.

[ViktorHofer]

In the aspect of not reinventing the wheel, what speaks against continuing to use the semantic-versioning-analyzer together with the in-built package validation? The analyzer provides package version suggestions vs. package validation validates compatibility of your packaged assets.