[bug]: Please tag a new major version when introducing BC breaks

[NiklasBr]

Description

The recent version update from 4.41.1 to 4.42.0 contained breaks which is in violation of semantic versioning.

It is okay to introduce BC breaks.

But please please do not tag a new minor version, instead tag a new major version.

Client

All

Version

4.42.0

Relevant log output

[Fluf22]

Hi @NiklasBr, thanks for raising this: we do agree with you.

As we aim to follow semantic versioning, we indeed understand how important stable minor releases are for our users, for you.

That said, we want to be transparent about why some breaking changes slipped into minor versions in the v4 lifecycle.
In some cases, the types exposed by the client didn't match the actual data returned by (or expected by) the Algolia REST API. We opted to fix those in minors rather than ship known-incorrect types until the next major, which we felt would cause more confusion downstream.

We know these are not great excuses for breaking semver. Just context on the tradeoffs we made.
We want you to know we're working on being more disciplined about this going forward, and we appreciate you holding us accountable.

If you hit a specific upgrade breakage, feel free to drop the details here and we'll help sort it out.

[NiklasBr]

Thanks for your response. Resolved internally for now by adjusting composer.json to

-    "algolia/algoliasearch-client-php": "^4.25",
+    "algolia/algoliasearch-client-php": "<4.42",

I think this could have been resolved with #[Deprecated] or trigger_error(..., E_USER_WARNING) in conjunction with class inheritance on the incorrect types versus fixed ones.