Limited auto updating of software packages is often done in the software world when
semantic versioning is being followed. The issue is a lot of plugin updates have rolled out from devs on uMod that do not follow semver. That is, backwards incompatible changes are being released without updating the plugin's major version number.
All of the following would be considered backwards incompatible changes:
- Data is deleted
- Config from previous version of the plugin is no longer compatible (requires consumer to delete it)
- A feature is removed
- A feature now requires another plugin to be installed
- A feature now requires a permission when it did not previously
- A feature now is now disabled by default due to a new config option being introduced (the default value of new config options should mimic the previous behavior or the change is considered backwards incompatible)
Basically anything that requires the consumer to do something is essentially a backwards-incompatible (or "breaking") change. We could do better to educate uMod plugin devs on how to follow good versioning practices.