Several patch releases contain breaking changes

[mdenburger]

Describe the bug
Several patch releases now contain breaking API changes, which violates semantic versioning.

Expected behavior
From version 1.0.0 onwards I would expect that every patch release is fully backwards compatible, and upgrading is a no-brainer. New features would increase the minor version (0.1.0, 0.2.0, etc). Any backwards incompatible change would lead to a new major version (2.0.0, 3.0.0, etc.).

Writing "THIS RELEASE CONTAINS BREAKING CHANGES" in the release notes is a big smell. Whether a release contains breaking changes should be communicated via the semantic version number.

[iamthesiz]

I'm not sure how I missed this. I will update as soon as possible. My sincerest apologies if this has caused any troubles.