announcing potentially breaking changes in new minor releases

[jeremypress]

Hi Next team,
When upgrading our app to a newer version of next, we noticed that a polyfill for setImmediate was removed (see #10612). Although this function isn't supposed to be used in the browser, we unfortunately have to use it based on another package we rely on.

In the PR review a team member mentioned how this is technically a breaking change. I totally understand this not triggering a major release, as this function shouldn't be used in the browser, and probably only affects a small number of users. But would it be possible to mark these changes in some way such that library users who are doing an upgrade can find potentially breaking changes faster? Maybe a label for "potentially breaking" changes, or something in the commit message that can be parsed easily? This would drastically reduce frustration when experiencing a break going up to a minor version.

Thanks for everything y'all do!