Go: Go 1.28 Opens as Edge Cases Get Cleaned Up
Go 1.28 development officially kicked off this week, while a cluster of fixes tightened up parsing and network-facing edge cases in the standard library, including a build constraint bug, an HTTP file server redirect issue, and a server body-handling fix.
Duration: PT2M35S
Episode overview
This episode is a short developer briefing from Go.
It explains recent repository work in plain language.
- Show: Go
- Published: 2026-07-15T13:06:57Z
- Audio duration: PT2M35S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's July 15th, 2026, and this is Go.
The headline today is the formal opening of Go 1.28 development, paired with a batch of quiet but important correctness fixes across the standard library.
Starting with the release cycle: Michael Matloob's commits, 7449936 and 6c87434, mark the traditional start of a new Go version — copying over the documentation template and bumping the internal version number to 1.28. If you track Go's release calendar, this is the signal that the clock has started.
The bigger theme, though, is a run of parsing and matching bugs getting fixed before they cause real trouble. PR 80407 from goto1134 fixes how the build system's GoVersion function reads version tags — previously, any tag that merely contained the substring "go1." anywhere, like "notgo1.21," was misread as a real…
On the reliability side, Damien Neil's net/http change, f5c3217, fixes a subtle bug where the server assumed a request's body type never changes as it passes through middleware. If middleware wraps or replaces the body, the server could mishandle connection reuse — the fix adds explicit tracking of the original body…
Smaller but worth knowing: Alan Donovan's std cleanup,…
Nearby episodes from Go
- Tightening the Compiler, Documenting the Edges
- Weekly Recap - Documentation Cleanup and a Root Security Fix
- Documentation Debt and the Testing Package's Rough Edges
- The Great Doc Cleanup
- Consistency Fixes Across the Toolchain
- Root Security Fix and a Network-Free Test Suite
- Tooling Fixes Tighten Edge Cases
- Regex Engine's Stale Flag Bug