Skip to content

Consider adding Package Validation to better identify breaking changes #119

@udlose

Description

@udlose

Package validation tooling allows library developers to validate that packages are consistent and well formed. It provides the following checks:

  • Validates that there are no breaking changes across versions.
  • Validates that the package has the same set of public APIs for all the different runtime-specific implementations.
  • Catches any applicability holes.

You can run package validation either as an MSBuild task or using the Microsoft.DotNet.ApiCompat.Tool global tool. If your app isn't packable, use assembly validation instead.

See Package Valdiation

Probably a good candidate for "good first issue"!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions