At Expedia, we were a gigantic perforce repository, but the trend has moved to hundreds of smaller repositories and applications hosted in enterprise github. P

At Expedia, we were a gigantic perforce repository, but the trend has moved to hundreds of smaller repositories and applications hosted in enterprise github. Package management is simple, we push common packages into sonatype nexus with semantic versioning. Personally I prefer strong versioning and allowing teams to upgrade common libraries at their own pace, but we've had a few times where we needed to quickly upgrade every repository (i.e., a security patch). You have a few options: 1. You can unpublish the old dependency, breaking all builds until they upgrade. (Frowned upon) 2. You can write a script that identifies all repository owners that depend on you and send out a upgrade by X date email. 3. You can script pull request creation and submit hundreds of pulls to upgrade the dependency. So far, things have worked out well, and I never want to go back to the monorepo.