It was actually done on purpose because there is a bug in versions prior to 2.0.10 where the comparison script isn't comparing correctly and the only way to let you know that it is outdated is to bump up the major version to 3.0.10 so that the comparison will work.

Since we use semantic versioning, direct comparison between 2.0.9 and 2.0.10 will not work. It was thinking that 2.0.9 is later than 2.0.10

gotcha, as long as it makes sense to you!

Thanks Haki Saki. We appreciate your undestanding on this.