Not really tested that, but I remember that version_compare deals with complex version compares.When dealing with a version string such as 1.1.1 or 1.2.13 or 2.0a, 2014-03-22 or 1.3.4 Beta 10 it's not really possible to accurately calculate which string represents the newest version. So, all the logic does is see if the two version strings (the one in the RM and the one installed) are different. If they are different, it assumes that the RM has a new version.
So, nothing at all to do with 1.3 and is as designed. Best thing to do is "Skip this update" so it will ignore it until the number changes again.
We use essential cookies to make this site work, and optional cookies to enhance your experience.