That doesn’t feel scalable to me. I’d imagine some dependencies at Google run to hundreds of clients.
To take an OSS view, some packages run to hundreds of thousands. Imagine if the maintainers of react had to fix all their clients.
It’s still not scalable in the sense that the downstream can make any change they want. They are restricted to changes they can either manually or automatically apply to client code in a reasonable amount of time. But that’s the trade off for being a heavily depended on library (which a lot of the time is an explicit decision).
Is it really though? Sure, it's technically possible, but it feels like a massive burden to place one on dependency.
Not only do you have to maintain your own lib, but you have to understand how every other project uses it.
Shouldn't the person/team who makes a change take ownership of fixing any breakage it causes, rather than passing the buck to their customers?
It sounds like the real issue isn't anything as technical as monorepos-vs-polyrepos or software versioning policies, but rather a management and culture problem?