Go 公式が公開している Go Modules に関するドキュメントを日本語訳するプロジェクトです。
A tutorial of short topics introducing functions, error handling, arrays, maps, unit testing, and compiling.
You can collect related packages into modules, then publish the modules for other developers to use. This topic gives an overview of developing and publishing modules.
When you develop modules for use by other developers, you can follow a workflow that helps ensure a reliable, consistent experience for developers using the module. This topic describes the high-level steps in that workflow.
When you're developing modules to publish for others to use, you can help ensure that your modules are easier for other developers to use by following the repository conventions described in this topic.
A major version update can be very disruptive to your module's users because it includes breaking changes and represents a new module. Learn more in this topic.
When you want to make a module available for other developers, you publish it so that it's visible to Go tools. Once you've published the module, developers importing its packages will be able to resolve a dependency on the module by running commands such as go get.
A module's developer uses each part of a module's version number to signal the version’s stability and backward compatibility. For each new release, a module's release version number specifically reflects the nature of the module's changes since the preceding release.
A detailed reference manual for Go's dependency management system.
Reference for the directives included in a go.mod file.