Semantic releases to prevent breaking changes causing issues

What would you like to be added:

The 0.22.0 release introduced breaking changes, which violates the expectations most users have for a minor version update. Many teams use tools such as Renovate to automatically apply non-major updates, assuming they are backward compatible.Breaking changes in a minor release can therefore cause unexpected outages and additional operational effort.Please consider releasing a 1.0.0 version and adhering to Semantic Versioning principles going forward, so that users can rely on version numbers to accurately reflect compatibility guarantees.

Why is this needed: