> but with multiple repos someone can commit a breaking change and a dependent repo won't know about about it until days, weeks or even months later; the perso

> but with multiple repos someone can commit a breaking change and a dependent repo won't know about about it until days, weeks or even months later; the person responsible for fixing it has no idea what really changed or why; and he has a broken build until he does figure it out. Isn't that the whole point of versioning? If there is a breaking change only the repo's using the latest version will see it. At which point they can submit a bug report before any of that code enters production. I still agree that avoiding all of that is preferred.