Hi @RadekWroblewski,
Just heard back from our API team, and we will be deploying a fix on Tuesday to revert this change. So sorry for this!
I will update the release notes when it is updated. It should only impact the complexity error, but please let me know if you see it for any others.
Best,
Rachel