How to be resistant against need to recompile materials

[yakovliev-hover]

Imagine sutuation

• You have your library or SDK that uses Filament and requires 1.52 version. And has inside compiled .filamat files compatible with this version.
• Third-party app uses your SDK, and also it has its own version of filament, for example, 1.56
• During compilation, Gradle will take 1.56 version during resolving dependencies
• So, code from your SDK will not be able to work, because it will throw a panic with the message: "reason: Material version mismatch. Expected 56 but received 52."

Is this possible to make code in the SDK resistant against such changes? What best practices can you suggest to mitigate risks that something will break due to changes version of filement and materials compatibility