Do not use a smaller version number to replace the current larger one

[PeterDaveHello]

1. The version field in package.json should be the largest stable version number, sometimes, the libs may have multiple release lines, like jquery, have both v1.x and v2.x versions, and I think we should not use a smaller number to replace the larger one even the smaller one was released much recently, or the users may misunderstand that we have the versions with larger versions.
2. Once a lib been added, we usually add the newest version only, and the updater will grab the old versions, in this situation, of course we should not use the old version number to replace the new one.