Who contributed to Go on August 3, 2026?

2 developers shipped this update, including Darren Carreras and Cuong Manh Le.

What were the notable Go updates?

cmd/compile: avoid range clear when target depends on index and cmd/compile: change disjoint to use types recorded in the Store operations.

@golang

Go and the standard library - backend infrastructure at scale

github ↗

Pick a date

Topics: Go Infrastructure Full archive →

The Wire · Showcase

GO COMPILER TIGHTENS RANGE-CLEAR SAFETY CHECKS

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

2 people shipped this

Darren Carreras @carrerasdarren-cell 1 cited

Cuong Manh Le @cuonglm 1 cited

The Go compiler just blocked a subtle optimization that could corrupt memory when loop variables depend on cleared values.

The range-clear optimization, which replaces manual loops with direct object clearing, has been restricted to prevent data corruption [1]. The fix requires the range index to remain stack-local and ensures the index itself doesn't appear in the target being cleared, stopping later iterations from accidentally selecting different objects. In parallel, the compiler's disjointness analysis now uses types recorded during Store operations rather than relying on separate type tracking [2], tightening memory safety guarantees across the optimization pipeline. Together, these changes represent Go's continuing effort to make high-performance optimizations safer by default. The compiler team has now built in protections that catch edge cases where optimization assumptions break down.

Action items

→ Monitor next Go release for these compiler hardening changes golang/go [monitor]

References

[1] cmd/compile: avoid range clear when target depends on index golang/go
[2] cmd/compile: change disjoint to use types recorded in the Store operations golang/go

Quick answers

What shipped in Go on August 3, 2026?: The Go compiler just blocked a subtle optimization that could corrupt memory when loop variables depend on cleared values. In total, 2 commits landed.
Who contributed to Go on August 3, 2026?: 2 developers shipped this update, including Darren Carreras and Cuong Manh Le.
What were the notable Go updates?: cmd/compile: avoid range clear when target depends on index and cmd/compile: change disjoint to use types recorded in the Store operations.

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

@golang Aug 1

GO COMPILER FIXES MIPS64 POINTER BUGS, SHRINKS BINARIES ON AMD64

Brad Fitzpatrick landed a stack object alignment fix that uncovers and fixes a latent mips64le pointer offset bug while accidentally making amd64 and arm64 binaries smaller.

go 11 shipped

Elsewhere on the wire

AI Agents Aug 6

LANGCHAIN HARDENS ANTHROPIC TOOL CALLING AND GIT CREDENTIALS AS OPENHANDS SHIPS 1.10.0

LangChain fixed a critical credential leak in evaluation runs while Anthropic tool schemas get proper fallback handling, as three major agent frameworks push releases across the ecosystem.

ai-agents 54 shipped

Local LLMs Aug 6

OLLAMA FIXES KV CACHE CORRUPTION, LLAMA.CPP HARDENS FILE SEARCH, VLLM KILLS MOE LEGACY CODE

Ollama patched a critical cache corruption bug that corrupts lazy snapshots during multi-request prefills, while llama.cpp hardened Windows junction traversal and vLLM removed 14 hardcoded MoE shards across quantization methods.