Skip to content

Commit

Permalink
doc: add 2020.2.2 release notes
Browse files Browse the repository at this point in the history
(cherry picked from commit b01bf20)
  • Loading branch information
dominikh committed Feb 19, 2021
1 parent 16f40c1 commit 034c552
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 2 deletions.
14 changes: 14 additions & 0 deletions doc/2020.2.html
Expand Up @@ -11,6 +11,7 @@
<li><a href="#checks-changed">Changed checks</a></li>
</ul></li>
<li><a href="#2020.2.1">Staticcheck 2020.2.1 release notes</a></li>
<li><a href="#2020.2.2">Staticcheck 2020.2.2 release notes</a></li>
</ul>

<h2 id="performance-improvements">Performance improvements</h2>
Expand Down Expand Up @@ -579,3 +580,16 @@ <h2 id="2020.2.1">Staticcheck 2020.2.1 release notes</h2>
See the <a href="https://blog.golang.org/path-security">Command PATH security in Go</a> article by the Go authors for more information on this potential vulnerability.
</li>
</ul>

<h2 id="2020.2.2">Staticcheck 2020.2.2 release notes</h2>

<p>
This release fixes a rare crash in Staticcheck, reduces the number of false positives, and adds support for Go 1.16's <code>io/fs.FileMode</code> type.
</p>

<ul>
<li>{{ check "SA9002" }} now supports the new <code>io/fs.FileMode</code> type in addition to <code>os.FileMode</code>.</li>
<li>Various checks no longer crash when analyzing nested function calls involving multiple return values.</li>
<li>{{ check "SA1006" }} no longer flags <code>Printf</code> calls of the form <code>Printf(fn())</code> when <code>fn</code> has multiple return values.</li>
<li>Staticcheck now understands the effects of <code>github.com/golang/glog</code> on a function's control flow. </li>
</ul>
4 changes: 2 additions & 2 deletions doc/staticcheck.html
Expand Up @@ -22,12 +22,12 @@ <h2 id="installation">Installation</h2>
<p>
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.
If you're still using a GOPATH-based workflow, then the above command will instead fetch the master branch.
It is suggested that you explicitly check out the latest release tag instead, which is currently <code>2020.2.1</code>.
It is suggested that you explicitly check out the latest release tag instead, which is currently <code>2020.2.2</code>.
One way of doing so would be as follows:
</p>

<pre><code>cd $GOPATH/src/honnef.co/go/tools/cmd/staticcheck
git checkout 2020.2.1
git checkout 2020.2.2
go get
go install
</code></pre>
Expand Down

0 comments on commit 034c552

Please sign in to comment.