Staticcheck 2019.2.1

The 2019.2 release has an unfortunate bug that prevents staticcheck from running on 32-bit architectures, causing it to crash unconditionally. This release fixes that crash.

Staticcheck 2019.2

Staticcheck 2019.2 brings impressive performance improvements, many new and improved checks, and various small improvements to its command line.

Read the full changelog at https://staticcheck.io/changes/2019.2

Staticcheck 2019.1.1

The 2019.1.1 release fixes some minor bugs and improves the performance of the U1000 check:

• The ST category of checks no longer flag style issues of aliased types when the aliased type exists in a package we aren't explicitly checking. This avoids crashes and erratic error reports.
• Compiler errors now have correct position information.
• A crash in the Stylish reporter has been fixed.
• We no longer flag unused objects that belong to cgo internals.
• The U1000 check has been optimized, reducing its memory usage and runtime.

Staticcheck 2019.1

Staticcheck 2019.1 makes some major changes to the structure of the tools. Please make sure to read the full changelog before deploying it.

Staticcheck 2017.2.2

Staticcheck 2017.2.2 fixes minor issues in unused, keyify and staticcheck:

• unused: correctly apply the NoCopy exemption when using the -exported flag.
• keyify: support external test packages (package foo_test)
• staticcheck: disable SA4005 – the check, in its current form, is prone to false positives and will be reimplemented in a future release.

Staticcheck 2017.2.1

Staticcheck 2017.2.1 fixes a small bug in the detection of deprecated objects, because of course no release can go without bugs!

The (admittedly very short) full changelog:

• Staticcheck 2017.2 made the detection of deprecated objects Go-version aware. Unfortunately, this only worked correctly for fields and methods, but not package-level objects. This release fixes that.

Staticcheck 2017.2

The 2017.2 release of the staticcheck suite of tools focuses on reducing friction – fewer false positives, more tools for suppressing unwanted output, and JSON output for easier integration with other tools.

The full changelog can be found at https://staticcheck.io/changes/2017.2