upgrade-notes-analyzer

To detect breaking changes in a pull request, analyze the PR diff and metadata to identify removed methods, modified constructors, and removed GraphQL fields. This process automatically categorizes potential issues for actionable upgrade notes.

Tracking feature movements from project-base to packages involves analyzing PR diffs to differentiate between actual code removals and structural migrations. This determines if a feature was relocated rather than deleted.

Yes, you can determine the scope of PR changes by analyzing the diff content. This analysis infers whether the modifications affect the backend, the storefront, or both, providing clear impact boundaries for upgrade notes.

The best way to generate actionable upgrade notes from a GitHub PR is to automate the analysis of pull request differences. This identifies breaking changes, feature movements, and scope shifts to streamline the release process.

Yes, this breaking change analyzer works with GraphQL schema modifications by detecting removed GraphQL fields during the PR diff analysis. It categorizes these schema alterations to ensure they are documented in the upgrade notes.

Automated PR analysis for release notes relies strictly on the provided pull request diff and metadata. It cannot infer external context or undocumented dependencies, meaning its scope determination is limited strictly to the submitted code changes.