I have no idea what you are talking about. There is nothing in Go that prevents people from making breaking changes to a package - and therefore breaking chang

I have no idea what you are talking about. There is nothing in Go that prevents people from making breaking changes to a package - and therefore breaking changes happen. I'll trust my real-world observations of broken dependencies over your assertion that they can't happen. My point is if you're not tracking the version of your dependencies, it can be hard to even know what versions to go back to to get something that compiles. It may not be enough to just roll back the package with the breaking change, since you may have other dependencies that have been updated to depend on the new version. The only way to reliably be able to compile your program in the future is to record the exact versions of all your dependencies.