0.9.3 depends on jackson-databind 2.13.3. 0.9.4 moved to 2.15.2.

Jackson's own release notes call 2.13 the "last branch for Android SDK 21+", with "SDK 26 minimum for 2.14". So that dependency bump raised the minimum Android API of this library from 21 to 26, which breaks API 21-25 - Android 5.0 through 7.1. The release notes do not mention it.

On any device below API 26 an app using this library now dies as soon as an ObjectMapper is constructed (verified on Android 7.0):

java.lang.NoClassDefFoundError: Failed resolution of: Ljava/lang/BootstrapMethodError;
    at com.fasterxml.jackson.databind.util.ExceptionUtil.isFatal
    at com.fasterxml.jackson.databind.ObjectMapper.<clinit>
    at org.msgpack.jackson.dataformat.MessagePackFactory...

This is not something consumers can work around by pinning jackson alone: MessagePackGenerator calls a GeneratorBase constructor that only exists from jackson-core 2.15, so forcing jackson 2.14 or lower fails with NoSuchMethodError while serializing. The only option left is pinning this library back to 0.9.3.

It reaches Android users indirectly too - the SignalR Java client depends on this artifact, so Android apps get it without ever choosing it.

Could you either document the minimum Android API in the README, or keep a line that stays on jackson 2.13 for Android consumers? Right now the constraint is invisible until an app crashes in production on older devices.