Not every OS connected to the internet can afford the risks of bad updates (which are far more common than proponents think/claim)
I suspect having this requirement would also greatly improve API design...
Since user interfaces (in particular) are not cleanly separated from the underlying system on personal devices, updates end up deploying both. I'd love for my family to get an updated browser or messaging client that only addresses issues around, say, the SSL implementation or HTTP or Unicode handling that specifically address security concerns. And then separate updates that alter the interface which become (somewhat) opt-in updates (though eventually they will be effectively mandatory). But that's not the reality of software development.
A major version change (eg UI rewrite or API breakage is an exception).
I don’t get the constant breakage the rest of HN seems to get, so there is no reason to pay the cost of manual updates.
But if your app updates with minimal inconvenience, good for you. In fact it comes in handy when the update adds new features or improves performance.