There's a reason why we don't do Continuous Delivery in a high reliability embedded context: the costs of bugs can be very high if it turns out to brick the device or physically damage it. As the other poster put it, it's continuous beta, and I personally am not a fan.
I like my releases thoroughly tested.
You updated some third party libraries, and maybe there's some subtle thing that changed in them to cause a break. Maybe that refactor wasn't zero impact the way it was intended to be. As a user, sure I want to know about third party libs being updated. All of that is useful information for us to decide to take the update or not. Back in the good old days it was all information everybody gave as a matter of course. These days, especially on phones, it's opaque and you're forced to take it whether you want to or not.
edit: and the interface changing out from under us unexpectedly is incredibly off-putting. I hate that these days I never know when an application I use every day is going to decide to remove its menus or something similarly asinine inflicted on me because that's the latest trend in UX design.
I like my releases thoroughly tested.
You updated some third party libraries, and maybe there's some subtle thing that changed in them to cause a break. Maybe that refactor wasn't zero impact the way it was intended to be. As a user, sure I want to know about third party libs being updated. All of that is useful information for us to decide to take the update or not. Back in the good old days it was all information everybody gave as a matter of course. These days, especially on phones, it's opaque and you're forced to take it whether you want to or not.
edit: and the interface changing out from under us unexpectedly is incredibly off-putting. I hate that these days I never know when an application I use every day is going to decide to remove its menus or something similarly asinine inflicted on me because that's the latest trend in UX design.