The API versioning number was not updated correctly at the release.
This lead to a wrong soname.

This is fixed now