8 don’t think anyone is suggesting this approach be used by typical users of OH. For the most part it is users on the Snapshots who will be doing this and they will discover and report the problems you mention as their upgraded system generates errors. Those running the snapshot are, by definition, alpha testers. It is unreasonable for an alpha testers to expect always a fully documented and automated upgrade process. But the approach above does help make their lives a little easier all the same.
Is it possible to also check if a binding has been updated? Both verified , on the market place and on github?
The version number of all the official bindings will move forward with the relase version number of the core. The only way to know what changes are included in a given release number is to watch the merged PRs on github. I don’t know how versioning is managed on the IoT marketplace.
The script from #1 from @kubawolanin doesn’t seem to work anymore. Probably because of the milestone build.
2018-05-23 15:23:45.431 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Error during the execution of startup rule 'Check for openHAB distro updates': For input string: "Milestone Build"