3 ms·
The thing is, the advantages of depending on HEAD vs. versioning dependencies have little to do with monorepo vs multiple repos. That is more a concern that dep
by tsimionescu 6y ago
The thing is, the advantages of depending on HEAD vs. versioning dependencies have little to do with monorepo vs multiple repos. That is more a concern that depends on how your VCS is managed and how your build system interacts with your VCS, outside of Go tooling.
With normal build/package management systems, nothing stops you from setting up your CI/CD system to pick up the latest from master in 20 repos, and nothing stops you from configuring maven to pick up dependencies from different moments in history from various places in your monorepo.
Also, this whole 'build everything from head' can't work when shipping versioned software to customers that demand patches and security updates, unless you have absolutely perfect test coverage AND absolutely perfect backwards compatibility, up to the internal API level. This would be like shipping the latest kernel to fix a security problem on a 5 year old system running 2.something.