Breaking Change in Patch Release

[murzart]

Description

Release 2.9.1 introduced a breaking change, violating Semantic Versioning (SemVer). According to SemVer, patch releases should only include backwards-compatible bug fixes.

Tools like Renovate and Dependabot automate the process of updating dependencies in a project. They rely heavily on Semantic Versioning (SemVer) to determine which updates are safe to apply automatically and which ones require manual intervention. When a library or package violates SemVer by introducing breaking changes in a patch release, it can have significant implications for these tools and the projects that use them.

Please do a proper major release if you make breaking changes.

Additional context

No response

Validations

• Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.

[xuri]

Apologies for the disruption and thank you for your issue. I will following semantic versioning rules next release.