Add 2020.1.5 release notes

dominikh · Jul 30, 2020 · ce9d960 · ce9d960
1 parent e18389c
commit ce9d960
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 1 deletion.
diff --git a/doc/2020.1.html b/doc/2020.1.html
@@ -11,6 +11,7 @@
   <li><a href="#2020.1.2">Staticcheck 2020.1.2 release notes</a></li>
   <li><a href="#2020.1.3">Staticcheck 2020.1.3 release notes</a></li>
   <li><a href="#2020.1.4">Staticcheck 2020.1.4 release notes</a></li>
+  <li><a href="#2020.1.5">Staticcheck 2020.1.5 release notes</a></li>
 </ul>
 
 <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>
 <p>
   You can find more information about this in the <a href="https://github.com/golang/protobuf/issues/1077">upstream issue</a>.
 </p>
+
+<h2 id="2020.1.5">Staticcheck 2020.1.5 release notes</h2>
+
+<p>
+  This release fixes a <a href="https://github.com/dominikh/go-tools/issues/806">crash in the pattern matching engine</a>
+  and a <a href="https://github.com/dominikh/go-tools/issues/733">false positive in SA4006</a>.
+</p>
diff --git a/doc/staticcheck.html b/doc/staticcheck.html
@@ -22,7 +22,7 @@ <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 branch instead, which is currently <code>2020.1.4</code>.
+  It is suggested that you explicitly check out the latest release branch instead, which is currently <code>2020.1.5</code>.
   One way of doing so would be as follows:
 </p>