cybercyst/go
1
0
Fork 0
mirror of https://github.com/golang/go.git synced 2025-05-05 23:53:05 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

updated existing mention of #26238 to indicate it is now closed; added mention of 'go get -u=patch'; added benefit of running 'go test ...' after upgrading; added mention of 'go help module-get'

thepudds 2018-07-25 12:08:34 -04:00
parent 53c5f51f03
commit ee879c5322
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Modules.md

@ -27,7 +27,7 @@ Go modules must be [semantically versioned](https://semver.org/) in the form `v(
The major version of a module must for now be included in both the module path and the package import path if the major version is v2 or higher. Module versions of v1 and v0 must not be included in the path. Modules with different paths are different modules. Thus `me.io/mymod` is different then `me.io/mymod/v2` and may import packages from one major version to another major version.
The behavior of modules for existing packages with post-`v1` tags is still in flux; see [issue 26238](https://golang.org/issue/26238) for discussion.
The behavior of modules for existing packages with post-`v1` tags is still in flux; an important related recent change was [issue 26238](https://golang.org/issue/26238), which substantially [improved the behavior](https://github.com/golang/go/issues/25967#issuecomment-407567904) for existing packages with post-`v1` tags.
### Modules
@ -115,7 +115,14 @@ To create a `go.mod` for an existing project, follow the following steps.
### Updating Dependencies
To update all transitive dependencies of the current module to the latest version, run `go get -u`.
To update all transitive dependencies of the current module to the latest version:
* run `go get -u` to use newer minor or patch releases
* run `go get -u=patch` to use newer patch releases
After updating, you may then want to run the tests again for all imported modules to check for incompatibilities:
```
$ go test ...
```
## Additional Resources
@ -124,6 +131,7 @@ To update all transitive dependencies of the current module to the latest versio
* Current [official modules documentation on tip](https://tip.golang.org/cmd/go/#hdr-Modules__module_versions__and_more)
* For more about modules, see 'go help modules'
* For more about the 'go mod' command, see 'go help mod'
* For more about the behavior of 'go get' when in module-aware mode, see 'go help module-get'
* The initial ["Go & Versioning"](https://research.swtch.com/vgo) series of blog posts by Russ Cox
* Official [Versioned Go Modules Proposal](https://golang.org/design/24301-versioned-go) (last updated March 20, 2018)