moq-analyzers-rule-lifecycle

To add a new analyzer rule in Moq.Analyzers, you must update both the project code and its accompanying documentation. This ensures the new diagnostic rule is properly registered and discoverable for consumers.

Modifying a shipped Moq analyzer rule requires updating its severity or category settings and then preparing the project for a subsequent release. This maintains consistency across deployed analyzer versions.

Releasing Moq.Analyzers relies on a specific versioning model to track diagnostic rule changes. The process involves executing defined release steps and performing necessary verifications before publishing a new package version.

You need to maintain release notes whenever adding new rules, modifying existing ones, or preparing a new Moq.Analyzers publication. This documentation tracks all lifecycle changes for maintainers and contributors.

Nerdbank.GitVersioning is a required dependency for managing the Moq.Analyzers release lifecycle. It provides the versioning infrastructure necessary to publish consistent and traceable analyzer rule updates.

When modifying shipped Roslyn analyzer rules in Moq, you must follow strict lifecycle steps to avoid breaking existing consumer builds. Changes require careful versioning and release preparation to manage compatibility.