@@ -80,6 +80,28 @@ To output a markdown compatible table, pass the `-style markdown` option
8080go list -u -m -json all | go-mod-outdated -style markdown
8181```
8282
83+ ** Important note for Go 1.14 users**
84+
85+ If are using Go 1.14 with vendoring you need to pass ** -mod=mod** or ** -mod=readonly** to the go list command otherwise
86+ you will get the following error:
87+
88+ ```
89+ $ go list -u -m -json all
90+
91+ go list -m: can't determine available upgrades using the vendor directory
92+ (Use -mod=mod or -mod=readonly to bypass.)
93+ ```
94+
95+ The following will work:
96+
97+ ```
98+ go list -u -m -mod=mod -json all | go-mod-outdated
99+ ```
100+
101+ ```
102+ go list -u -m -mod=readonly -json all | go-mod-outdated
103+ ```
104+
83105### Docker
84106In the folder where your go.mod lives run
85107```
@@ -141,10 +163,8 @@ There is a case where the updated version reported by the go list command is act
141163go-mod-outdated output includes a column named ** VALID TIMESTAMP** which will give an indication when this case happens,
142164helping application maintainers to avoid upgrading to a version that will break their application.
143165
144- ## Important notes
166+ ## Important note
145167
146- - Go's module system will be finalized in Go 1.13 version. Since this tool relies on the output of Go's list related to
147- modules, expect things to break.
148168- Upgrading an application is a responsibility of the maintainer of the application. Semantic versioning provides a way
149169to indicate breaking changes, but still everything relies on each module developer to apply correct version tags. Unless
150170there is a fully automated way to detect breaking changes in a codebase, a good practice to avoid surpises is to write
@@ -156,6 +176,7 @@ tests and avoid dependencies on modules not well maintained and documented.
156176- 1.11.x
157177- 1.12.x
158178- 1.13.x
179+ - 1.14.x
159180
160181## Supported operating systems
161182
0 commit comments