I find this goes against the go simplicity. I continually find that Maven & Gradle are much easier to use than Go's package management system for versioned dependencies.
That's 36 pages printed (try printing it), and includes the grammar for the go.mod file, information about the ecosystem of services available (module proxy, sumdb) and their protocol definitions, how to access and publish private modules, etc. It doesn't skimp on thoroughness anywhere.
Every place I worked, Java build pipeline has always been cumbersome, it's one thing that one guy knows and you're afraid to change it because it's complicated.
