How do we make breaking changes immediately visible

[surchs]

We use semver (and once goes in, this will be meaningful). We are in "initial development" which is defined as

Anything MAY change at any time. The public API SHOULD NOT be considered stable.

That's accurate, but maybe not very convenient for users. So we should discuss how we want to highlight meaningful breaking changes. Or if we want to soon move to a major version release and leave the development space.

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!

[alyssadai]

Now that we have our auto-release process set up, we can achieve this using our pr-minor-breaking and pr-major-breaking release labels (see also our template .autorc here). These should automatically organize breaking change PRs under a dedicated section in the changelog.