RepoJournal
Go

@golang

Go and the standard library - backend infrastructure at scale

Keep up with Go in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: Go Infrastructure Full archive →

The Wire · Showcase

VSCODE-GO TIGHTENS LINTING, REVIVE JUMPS 11 VERSIONS

By RepoJournal · Filed · About Go

The Go extension for VS Code is enforcing stricter TypeScript rules across the codebase while shipping a major update to its revive linter.

Hongxiang Jiang landed back-to-back linting improvements that eliminate unused variables and enforce promise handling in the extension [1] [2]. The first change removes dead parameters and unused local variables; the second enables the @typescript-eslint/no-floating-promises rule, marking unawaited promises with void to catch async bugs at lint time. In the same window, Chiman Jain bumped revive from v1.3.9 to v1.15.0 [3], a significant jump that brings 11 versions of improvements to the linting experience. On the core side, Michael Pratt clarified documentation in the new encoding/json/jsontext API [4] to explain that AvailableBuffer itself is safe, but manually constructing Values is error-prone. Peter Weinberger fixed a segmentation fault in gopls completion logic [5] that occurred during double-deslicing in generic function signatures. Jonathan Amsterdam added documentation coverage metrics to pkg.go.dev's evals page [6], making it easier to track which packages lack adequate godoc.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] extension/eslint.config.js: enable unused vars golang/vscode-go
  2. [2] extension: enable @typescript-eslint/no-floating-promises rule golang/vscode-go
  3. [3] src/goInstallTools: update revive to v1.15.0 golang/vscode-go
  4. [4] encoding/json/jsontext: clarify safety of AvailableBuffer golang/go
  5. [5] gopls/internal/golang/completion: avoid SEGV from double deslicing golang/tools
  6. [6] internal/frontend: display doc eval golang/pkgsite

Quick answers

What shipped in Go on August 8, 2026?
The Go extension for VS Code is enforcing stricter TypeScript rules across the codebase while shipping a major update to its revive linter. In total, 6 commits landed.
Who contributed to Go on August 8, 2026?
5 developers shipped this update, including Hongxiang Jiang, Chiman Jain, Michael Pratt, Peter Weinberger, and Jonathan Amsterdam.
What were the notable Go updates?
extension/eslint.config.js: enable unused vars, extension: enable @typescript-eslint/no-floating-promises rule, and src/goInstallTools: update revive to v1.15.0.

More from @golang

Daily updates, in your inbox

Follow Go

Keep up with Go in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?