Update UI incorrectly compares prelease semantic versions about gateway HOT 2 OPEN

This probably also explains #3054 since it doesn't think 1.1.0-beta.2 is newer than 1.1.0-alpha.2 (the output of the function is 0).

Note that this will mean users who installed a 1.1 pre-release won't be able to manually trigger an update to 1.1 in the UI, but their gateway will automatically update itself within 24 hours if automatic updates are enabled.

An alternative workaround is to manually run ./tools/check-for-update.sh on the command line.

from gateway.

See also https://github.com/WebThingsIO/gateway/blob/master/src/addon-utils.ts which uses yet another approach for comparing versions. For the purposes of checking add-on compatibility it currently ignores pre-release suffixes, but the semver library used there may be useful.

from gateway.