At my previous workplace we were using https://greenkeeper.io/ https://greenkeeper.io/ and locking dependencies, which i think may be the perfect compromise bet

At my previous workplace we were using https://greenkeeper.io/ https://greenkeeper.io/ and locking dependencies, which i think may be the perfect compromise between those 2 systems of organization. You get pinned dependencies, resulting in stable builds. For every package update (automatically scanned), you get a branch spawned w/ tests run if you've set up CI. It makes staying up to date easy when it's an easy upgrade (just merge a green branch!), and you get isolated knowledge up-front when a dependency has upgraded and you're gonna need to budget some time on it.