We had the same issue. Here @bozana supposed this might be related to the latest release’s version number not being updated properly:
The workaround now is to upgrade it through the standard plugin panel, not paying attention to the version number displayed.