I agree with you. Churn for churn's sake to make things marginally better. One man's refactoring is another man's refucktoring. Depending on a library could al

I agree with you. Churn for churn's sake to make things marginally better. One man's refactoring is another man's refucktoring. Depending on a library could also insert a record on the library's CI system to indicate the dependency. The library CI will ping a URL with a version number to indicate that "you need to re-test with this version". It would certainly make software more robust and evolvable. I've thought about it before and called it library mesh: https://github.com/samsquire/ideas2#10-library-mesh https://github.com/samsquire/ideas2#10-library-mesh