breaking-changes

To review pull requests for API breaking changes, analyze the PR descriptions, comments, diffs, and linked issues to identify potential compatibility modifications. This process assesses the severity and scope of identified breaks to prioritize reviews effectively.

A behavioral breaking change is an API modification in a pull request that alters existing compatibility and stability. It is identified by examining diffs and linked issues to evaluate the impact on the SDK's expected functionality.

Assess the impact of breaking changes between release tags by analyzing the range of merged pull requests for API modifications. This evaluates the severity and scope of the breaks to prioritize reviews and maintain compatibility standards.

Yes, you can update PR labels based on breaking change analysis by reconciling the labels with the assessment results. This checks and updates the labels to maintain compatibility standards, prompting user confirmation before applying changes.

Generate migration guidance for confirmed breaking changes by creating structured summaries of the analysis. This reporting classifies the breaks and provides actionable migration steps for release management.

Yes, this breaking change analysis specifically examines pull requests in the C# MCP SDK repository. It audits the PRs to ensure compatibility and stability within that particular development environment.