was wondering if its possible to make it save the config first of ? before updating if it need to,
as some plugin overwritte the cfg sometimes

A plugin should not be overwriting the config on a minor/patch update. If you want to disable those types of updates, you can in the config

birthdates

A plugin should not be overwriting the config on a minor/patch update. If you want to disable those types of updates, you can in the config

Indeed, plugins ideally should not update their config in a backwards incompatible way when only changing the version at the minor or patch level. However, the unfortunately reality is that this happens very often at the patch level, due to plugin developers not being aware of Semantic Versioning, or how to make configuration changes backwards compatible (which is actually pretty easy). Case in point, I saw one plugin updated today from 1.1.0 to 1.1.1 and the patch notes said "You may have to manually delete your config file". While educating developers through various mechanisms can help, that will take some time and we can't be sure how much that will succeed.

Because it can't be assumed that new plugins will follow Semantic Versioning, I suggest a whitelist as opposed to a blacklist approach. You can allow both, with the whitelist superceding the blacklist. I also suggest educating people who are downloading this plugin about this common issue, warning them of the consequences of blindly allowing automatic updates from all plugins.

I've had issues with configs being overwritten in various situations when they weren't expected and it's a real bummer hehe