Who contributed to Go on August 7, 2026?

7 developers shipped this update, including Michael Pratt, Daniel McCarney, Jonathan Amsterdam, Ethan Lee, Peter Weinberger, Hongxiang Jiang, and Carlos Amedee.

What were the notable Go updates?

cmd/compile/internal/ssa: constant fold math/bits functions, crypto/tls: implement -expect-extended-master-secret in bogo shim, and crypto/tls: add BoGo coverage for FIPS 140-3 EMS enforcement.

@golang

Go and the standard library - backend infrastructure at scale

github ↗

Pick a date

Topics: Go Infrastructure Full archive →

The Wire · Showcase

COMPILER OPTIMIZATIONS AND TLS HARDENING PUSH THROUGH GOLANG ECOSYSTEM

By RepoJournal · Filed 06:56 UTC on August 7, 2026 · About Go

7 people shipped this

Hongxiang Jiang @h9jiang 4 cited

Daniel McCarney @cpu 2 cited

Jonathan Amsterdam @jba 1 cited

Ethan Lee @ethanalee-work 1 cited

Michael Pratt @prattmic

Peter Weinberger @pjweinbgo

Carlos Amedee @cagedmantis

Go's compiler now constant-folds expensive math/bits operations at compile time, while crypto/tls hardens FIPS 140-3 enforcement and vscode-go cleans up its code lens architecture.

The compiler team shipped constant folding for RotateLeft, Sub64borrow, and Div128u operations [1], which means code using these functions on known constants will no longer pay runtime cost. This is particularly valuable in crypto and bit-manipulation-heavy workloads where these operations are common. Meanwhile, the TLS stack is tightening FIPS 140-3 compliance with new Extended Master Secret (EMS) coverage [2][3], ensuring that both positive and resumption tests now run where they were previously skipped. The gopls team synchronized semantic token capabilities with vscode-go [6][9], preparing both client and server to honor custom modifiers that language clients support. Over at vscode-go, Hongxiang Jiang removed legacy code lens provider complexity [8] and hardened the linter configuration to treat unused disable directives as errors [7], reducing future regressions. Package site is building out documentation coverage tooling [4] and integrating vector search into the frontend [5] to improve how users discover packages.

Action items

→ Review constant folding impact on crypto and math/bits-heavy code paths in your projects golang/go [monitor]
→ If running FIPS 140-3 mode, validate TLS resumption behavior against new test coverage golang/go [plan]
→ Update vscode-go and verify semantic token modifiers display correctly with gopls v0.24.0+ golang/vscode-go [plan]

References

[1] cmd/compile/internal/ssa: constant fold math/bits functions golang/go
[2] crypto/tls: implement -expect-extended-master-secret in bogo shim golang/go
[3] crypto/tls: add BoGo coverage for FIPS 140-3 EMS enforcement golang/go
[4] devtools/cmd/evaldoc: tool for doc coverage golang/pkgsite
[5] internal, cmd: integrate vector search into frontend golang/pkgsite
[6] gopls/internal/protocol/semtok: instructions for modifier/type changes golang/tools
[7] extension/eslint.config.js: report unused disable directives as error golang/vscode-go
[8] extension/src: remove base code lens provider golang/vscode-go
[9] extension/src/language: extend semantic token client capabilities golang/vscode-go

Quick answers

What shipped in Go on August 7, 2026?: Go's compiler now constant-folds expensive math/bits operations at compile time, while crypto/tls hardens FIPS 140-3 enforcement and vscode-go cleans up its code lens architecture. In total, 15 commits landed.
Who contributed to Go on August 7, 2026?: 7 developers shipped this update, including Michael Pratt, Daniel McCarney, Jonathan Amsterdam, Ethan Lee, Peter Weinberger, Hongxiang Jiang, and Carlos Amedee.
What were the notable Go updates?: cmd/compile/internal/ssa: constant fold math/bits functions, crypto/tls: implement -expect-extended-master-secret in bogo shim, and crypto/tls: add BoGo coverage for FIPS 140-3 EMS enforcement.

VSCODE-GO TIGHTENS LINTING, REVIVE JUMPS 11 VERSIONS

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

go 6 shipped

@golang Aug 6

GO PATCHES TEMPLATE INJECTION FLAW, HTTP/2 GOROUTINE LEAK

Go shipped a security fix for html/template that blocks JavaScript regexp injection attacks, while simultaneously addressing a goroutine accumulation bug in HTTP/2 transports that could exhaust memory on long-lived connections.

go 4 shipped

@golang Aug 5

GO FIXES BREAKING ABI REGRESSION AND LOCKS DOWN REVERSE PROXY COOKIE HANDLING

Go shipped a critical fix for an x86 ABI0 NOFRAME regression that broke existing code, while explicitly documenting that ReverseProxy does not sanitize forwarded cookies.

go 20 shipped

@golang Aug 4

SSH WINDOW CREDIT BUG COULD STALL CHANNELS; COMPILER REFACTORING SPLITS SSA PACKAGE

Go's SSH implementation leaks window credits on discarded extended data, potentially freezing channels, while the compiler team restructures its core SSA package to improve modularity.

go 30 shipped

Elsewhere on the wire

AI Agents Aug 8

LANGCHAIN PATCHES CLAUDE FILE TOOLS AND OPENAI CONTEXT ERRORS

LangChain shipped langchain-openai 1.4.2 with fixes for context window overflows and broken Claude rename operations, while OpenHands v1.11.0 adds per-run LLM cost tracking.

ai-agents 99 shipped

Local LLMs Aug 8

OLLAMA SHIPS BLOCK-DIFFUSION SPECULATIVE DECODING, SGLANG LAUNCHES KIMI K3 DAY-0

Draft models just got faster: Ollama merged DFlash block-diffusion speculative decoding that proposes entire token sequences in one forward pass, while SGLang shipped production-ready support for Kimi K3, a 2.8T-parameter multimodal LatentMoE that routes through a latent space with 896 experts.

+12

llms 263 shipped

@CachyOS Aug 8

CACHYOS AUTOMATION PUSHES BROWSER UPDATES ACROSS THE STACK

Five browser and utility packages shipped overnight with automated version bumps, while the Welcome interface gains Traditional Chinese support and translation cleanup hits the queue.

infra 51 shipped

Elixir & Phoenix Aug 8

ELIXIR PARSER GETS LEANER AS PHOENIX AUDITS DEAD CODE

Daniel Kukula shipped three consecutive optimizations to Elixir's date parsing pipeline, removing accumulators and intermediate allocations in a focused performance push [ref:1] [ref:2] [ref:3].