Despite the limitations mentioned in this article, my team prefers a monorepo. I said, if you have a better way for us to administrate this, please start a disc

Despite the limitations mentioned in this article, my team prefers a monorepo. I said, if you have a better way for us to administrate this, please start a discussion. If the pros outweigh the cons, we'll transition off. Under the old model (non-monorepo), you merge and release one repo. Then you have to open a pull request in another repo to do a dependency bump. That step is busy work that doesn't provide real value to the business, and it's something you need to regularly if all of your repos are being actively developed.