We should update the library to support Cairo 2.5.0.
Context
Many users are experiencing issues when trying to use our v0.8.1 release with Cairo and Scarb v2.5.0.
The problem is that v2.5.0 introduced breaking API changes, so it should have been v3.0.0 instead. This is leaking downstream to Scarb where the compatibility check fails to detect this version update as a breaking one, resulting in this error. You should not be allowed to use Contracts for Cairo <=0.8.1 with Cairo 2.5.0.
We should update the library to support Cairo 2.5.0.
Context
Many users are experiencing issues when trying to use our v0.8.1 release with Cairo and Scarb v2.5.0.
The problem is that v2.5.0 introduced breaking API changes, so it should have been v3.0.0 instead. This is leaking downstream to Scarb where the compatibility check fails to detect this version update as a breaking one, resulting in this error. You should not be allowed to use Contracts for Cairo <=0.8.1 with Cairo 2.5.0.