This is a good way to put it. I think the opposite is also true: going with many repos means you are committing to other teams being on their own to upgrade. It

This is a good way to put it. I think the opposite is also true: going with many repos means you are committing to other teams being on their own to upgrade. It’s difficult to know if you’ve fixed all downstream code if everything isn’t in one repo. That model makes sense for OSS. Not so sure about within companies.