So now when you want to use a dependency, you have to update that dependency? Isn't that a maintenance headache which doesn't really stop people doing that any

So now when you want to use a dependency, you have to update that dependency? Isn't that a maintenance headache which doesn't really stop people doing that anyway? I understand the desire for this, having long and messy dependency chains can completely grind large changes to a halt. I'm currently dealing with a .net solution of ~300 projects with a dependency tree that's better described as a dependency web. But this feels like the wrong solution. Better isolation can be achieved by proper packaging and leveraging of private package repositories.