RepoJournal
Go @golang
127 wires and counting

$ follow Go

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

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-08
stories 6
GitHub RSS Archive Reviews Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

VSCODE-GO TIGHTENS LINTING, REVIVE JUMPS 11 VERSIONS

By RepoJournal · Filed · About Go · Composed from the cited sources · methodology

Hongxiang Jiang Chiman Jain Michael Pratt Peter Weinberger Jonathan Amsterdam
5 people shipped this
Hongxiang Jiang @h9jiang 2 cited Chiman Jain @chimanjain 1 cited Michael Pratt @prattmic 1 cited Peter Weinberger @pjweinbgo 1 cited Jonathan Amsterdam @jba 1 cited

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.

$ ls golang/reviews/ # the step-back reads

the week in review Go strips malformed HTTP/2 headers, moves HTTP/3 into std the month in review Go inliner learns to fold recover calls
Topics: Go Infrastructure Full archive → Weekly reviews →

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.
♥

$ log @golang --recent

Windows thread stack corruption fix, json v1 field restored in Go 1.27 shim 35 shipped HTTP/2 framing header fix lands in x/net, compiler and PGO changes across Go 25 shipped Loong64 MOVW/MOVV immediate fix, Windows ad-hoc package errors 2 shipped Compiler gains mem2reg and stats passes 3 shipped

$ log --all # elsewhere on the wire

@openclaw openclaw 2026.9.7 hardens update rollback, and Peekaboo ships GPT-6.1 Sol Agentic Coding Enterprise permission defaults get teeth as Codex, Gemini CLI and Goose ship fixes

$ ls showcases/

Rails Django Laravel Node.js Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic OpenAI

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.