Stop letting update module update modules that introduce new dependencies

You can completely ruin your site when using update module. For example, updating commerce_coupon_beta4 to commerce_coupon_beta5 breaks everything. Beta5 introduces a new dependency and the unsuspecting user sees there's an update, they run update, and then they can never get passed update.php because of the new dependency that doesn't exist. They can't go and install the module because they can't get passed update.php.

Now yes, myself and others can go in and fix it but do you think a non-programmer user can do it? I think not.

You're able to force manual update of core so I think you should force manual update for modules that need special steps to update, like adding in dependencies.