File tree Expand file tree Collapse file tree 2 files changed +30
-2
lines changed Expand file tree Collapse file tree 2 files changed +30
-2
lines changed Original file line number Diff line number Diff line change 10
10
< li > < a href ="#2020.1.1 "> Staticcheck 2020.1.1 release notes</ a > </ li >
11
11
< li > < a href ="#2020.1.2 "> Staticcheck 2020.1.2 release notes</ a > </ li >
12
12
< li > < a href ="#2020.1.3 "> Staticcheck 2020.1.3 release notes</ a > </ li >
13
+ < li > < a href ="#2020.1.4 "> Staticcheck 2020.1.4 release notes</ a > </ li >
13
14
</ ul >
14
15
15
16
< h2 id ="introduction "> Introduction to Staticcheck 2020.1</ h2 >
@@ -192,3 +193,30 @@ <h2 id="2020.1.3">Staticcheck 2020.1.3 release notes</h2>
192
193
</ li >
193
194
</ ul >
194
195
</ p >
196
+
197
+ < h2 id ="2020.1.4 "> Staticcheck 2020.1.4 release notes</ h2 >
198
+
199
+ < p >
200
+ This release adds special handling for imports of the
201
+ deprecated < code > github.com/golang/protobuf/proto</ code > package.
202
+ </ p >
203
+
204
+ < p >
205
+ < a href ="https://github.com/golang/protobuf "> github.com/golang/protobuf</ a >
206
+ has deprecated the < code > proto</ code > package, but
207
+ their < code > protoc-gen-go</ code > still imports the package and uses
208
+ one of its constants, < q > to enforce a weak dependency on a
209
+ sufficiently new version of the legacy package</ q > .
210
+ </ p >
211
+
212
+ < p >
213
+ Staticcheck would flag the import of this deprecated package in all
214
+ code generated by protoc-gen-go. Instead of forcing the project to
215
+ change their project structure, we choose to ignore such imports in
216
+ code generated by protoc-gen-go. The import still gets flagged in code
217
+ not generated by protoc-gen-go.
218
+ </ p >
219
+
220
+ < p >
221
+ You can find more information about this in the < a href ="https://github.com/golang/protobuf/issues/1077 "> upstream issue</ a > .
222
+ </ p >
Original file line number Diff line number Diff line change @@ -22,12 +22,12 @@ <h2 id="installation">Installation</h2>
22
22
< p >
23
23
If you use Go modules, you can simply run < code > go get honnef.co/go/tools/cmd/staticcheck</ code > to obtain the latest released version.
24
24
If you're still using a GOPATH-based workflow, then the above command will instead fetch the master branch.
25
- It is suggested that you explicitly check out the latest release branch instead, which is currently < code > 2020.1.3 </ code > .
25
+ It is suggested that you explicitly check out the latest release branch instead, which is currently < code > 2020.1.4 </ code > .
26
26
One way of doing so would be as follows:
27
27
</ p >
28
28
29
29
< pre > < code > cd $GOPATH/src/honnef.co/go/tools/cmd/staticcheck
30
- git checkout 2020.1.3
30
+ git checkout 2020.1.4
31
31
go get
32
32
go install
33
33
</ code > </ pre >
You can’t perform that action at this time.
0 commit comments