Suggestion

Our Configurations and Maintenance > Versioning docs specify that changes to the recommended configs need to be marked as a breaking change. But nothing I can spot enforces that changes to recommended.ts or its friends be labeled as breaking change.

To help prevent slipups in the future, let's add some kind of automation that marks PRs as failing if they do touch a recommended config file and don't have the breaking change label.