It looks like updating the version number in library.properties and library.json was overlooked when creating the latest release. I'm not quite sure what impact this will be having for the library managers but it's certainly confusing!
Solved! Go to Solution.
Thank you for indicate.
This is reported to our SW team and fix will be made in Github later on