Clearly document possibly breaking changes

[dreusel]

Feature request

My request is that any updates that can reasonably be expected to break some use-cases (such are removal of some (previously deprecated or not) functions or properties) are marked in a consistent way so that they can easily be checked for by projects utilizing the library. Instead of having to consider every line in the changelog which is time-consuming and error-prone.
For example by adopting a policy to include something like "break:" or "(breaking)" in the description line. And possibly also repeating these changes in the 'minor' section of the changelog file.

This could also be a very helpful step in at some future point bumping to 1.0.0

What are you trying to achieve?

To easily know weather or not some version bump includes breaking changes for my use-cases

When you searched for similar feature requests, what did you find that might be related?

Someone sugested to bump to 1.0.0

[lovell]

Thank you for the suggestion, this is a sensible idea. The changelog for the next release has been updated via commit b7ff264 to list breaking changes first. We can continue to use this pattern in the future.