That might be good for developer health, but its crappy for user experience. And I've worked with some people that have literally wrote the book on CI/CD, so I

That might be good for developer health, but its crappy for user experience. And I've worked with some people that have literally wrote the book on CI/CD, so I fully understand the philosophy and benefits. You probably need to at least throttle your auto-updates so that users who are just on autopilot don't upgrade more than once a month unless there's a truly critical update (not critical to you, but critical to your users). You can more or less stagger them and if they haven't updated in a month plus or minus some random fuzz that they pop open the auto update and download the latest changes. That isn't CI/CD instant-feedback nirvana of every change, but you should dribble out enough changes to users in a few days to get enough feedback (this also limits the impact of any embarrassing critical regressions). And most Enterprise users tend to deeply hate auto updates unless you happen to be selling only into other CI/CD using Enterprises. You want them all on the latest and greatest so you don't have to deal with bugs, but they want stable software until they decide to bump it. We tried imposing auto updates on Enterprise customers and they really hated it. You're probably going to have to find some kind of compromise there. Although I will also agree that having Enterprise customers that you have to support stuck on 5 year old versions of your product can easily kill the product. But everyone has upgrade fatigue and you really need to listen to customers and find some kind of compromise.