File tree 2 files changed +9
-1
lines changed 2 files changed +9
-1
lines changed Original file line number Diff line number Diff line change 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
13
< li > < a href ="#2020.1.4 "> Staticcheck 2020.1.4 release notes</ a > </ li >
14
+ < li > < a href ="#2020.1.5 "> Staticcheck 2020.1.5 release notes</ a > </ li >
14
15
</ ul >
15
16
16
17
< h2 id ="introduction "> Introduction to Staticcheck 2020.1</ h2 >
@@ -220,3 +221,10 @@ <h2 id="2020.1.4">Staticcheck 2020.1.4 release notes</h2>
220
221
< p >
221
222
You can find more information about this in the < a href ="https://github.com/golang/protobuf/issues/1077 "> upstream issue</ a > .
222
223
</ p >
224
+
225
+ < h2 id ="2020.1.5 "> Staticcheck 2020.1.5 release notes</ h2 >
226
+
227
+ < p >
228
+ This release fixes a < a href ="https://github.com/dominikh/go-tools/issues/806 "> crash in the pattern matching engine</ a >
229
+ and a < a href ="https://github.com/dominikh/go-tools/issues/733 "> false positive in SA4006</ a > .
230
+ </ p >
Original file line number Diff line number Diff line change @@ -22,7 +22,7 @@ <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.4 </ code > .
25
+ It is suggested that you explicitly check out the latest release branch instead, which is currently < code > 2020.1.5 </ code > .
26
26
One way of doing so would be as follows:
27
27
</ p >
28
28
You can’t perform that action at this time.
0 commit comments