OK, one more change.
Put the min/max version numbers in pluginInfo.json in quotes. This helps fix the issue of comparing 1.1 vs 1.10. If we use just a float in JSON, those both will get converted to 1.1 in JavaScript. If we embed them in quotes, then we can compare them. I created a Javascript helper function CompareFPPVersions() to compare two version strings so that the code understands that v1.9 is less than v1.10. If the min/max version number is actually a number in the json, the script converts it to a string, but it is best to enter these as a string to begin with so we don't have issues with trailing zeroes being dropped.
Also, if you have a plugin that is compatible with v1.x, you can put the min version as 1.0 and the max as 1.9999. In the master branch, the version shows up as 2.1xxx where xxx is the commit number after the last tag, so using 2.9999 would catch all v2.x releases along with the master branch.