118 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-09-16
stories 18

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Unencrypted HTTP/2 stops canceling request contexts; localhost resolves to loopback

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

Two net fixes from Brad Fitzpatrick land in golang/go, one regressing requests over unencrypted HTTP/2 and one aligning the Go resolver with RFC 6761's treatment of localhost.

net/http: don't cancel request contexts on idle unencrypted HTTP/2 conns golang/go

by Brad Fitzpatrick

The unencrypted HTTP/2 path was handing the HTTP/2 server a context that gets canceled as soon as conn.serve returns, which now happens immediately because the serve goroutine parks, so every request context on an h2c connection was being canceled mid-flight. The fix passes the connection context instead, matching what the TLS ALPN path already did. If you run h2c servers, this is the one to pull.

net: resolve localhost names to loopback in the Go resolver golang/go

by Brad Fitzpatrick

RFC 6761 section 6.3 says resolution APIs should always return the loopback address for localhost and names under .localhost, and should not forward those queries to the configured caching DNS servers. The Go resolver did neither, resolving from the hosts file and querying upstream otherwise; it now follows the spec. Behavior change for anyone relying on hosts-file mappings or custom DNS entrie...

hash/adler32: add vectorized implementation for amd64 golang/go

by Alex Gaynor

An AVX2 kernel using the goexperiment.simd archsimd intrinsics processes 32 bytes per iteration via VPSADBW and VPMADDUBSW, deferring modular reduction across each nmax-bounded run of blocks. The arm64 counterpart adds a NEON path with the same 32-byte block and the same dispatch rules: AVX2 or NEON when available, scalar loop for inputs under 64 bytes and builds without the simd experiment.

go/ssa: preserve single-case receive assignment order golang/tools

by Li Jie

A single-case select was lowered like an ordinary assignment, which evaluates the left-hand side before the receive, while select semantics require the receive and communication to happen first. Receive is now evaluated before the assignment left-hand side is constructed, with the existing single-case fast path and SSA shape otherwise retained. Anyone reading SSA output for select-based code wi...

deploy: use Go 1.27.1 for builds and deployments golang/pkgsite

by Hana Kim

Go 1.27 is out, so pkgsite's _GO_VERSION moves off the release candidate to the latest 1.27 patch release, and the Docker Compose section of deploy/README.md no longer keeps a second hardcoded copy of the version. Elsewhere: gopls's resolve_target command lands with restrictions on qualified package paths and no Range or TextDocument inference yet, vulndb adds six reports, and golang/net's QUIC...

Quick answers

What shipped in Go on September 16, 2026?
Two net fixes from Brad Fitzpatrick land in golang/go, one regressing requests over unencrypted HTTP/2 and one aligning the Go resolver with RFC 6761's treatment of localhost. In total, 18 commits landed.
Who contributed to Go on September 16, 2026?
10 developers shipped this update, including Brad Fitzpatrick, Jake Bailey, Alex Gaynor, Hana Kim, Hongxiang Jiang, Alex Putman, Li Jie, and yungchoppa, and 2 more.
What were the notable Go updates?
net/http: don't cancel request contexts on idle unencrypted HTTP/2 conns, net: resolve localhost names to loopback in the Go resolver, and hash/adler32: add vectorized implementation for amd64.