The Wire · Showcase
GOPLS ASSEMBLY SUPPORT LANDS, GODEP REFRESH ROLLS ACROSS ECOSYSTEM
By RepoJournal · Filed · About Go
The Go toolchain just got smarter about assembly files, and a coordinated dependency update is rolling through every major repo simultaneously.
Gopls now supports CompiledAsmFiles in its cache.Package, closing a gap for projects that blend Go and assembly [1]. This lands alongside a coordinated refresh of golang.org/x dependencies across tools, benchmarks, perf, and net repos [2][3][4][6], all merged and auto-submitted in a single coordinated push. On the HTTP/3 front, golang/net implemented server read and write deadlines [5], finally enforcing ReadHeaderTimeout, ReadTimeout, and WriteTimeout on the server side. Two bugs in the main Go repo got squashed: gofmt was mangling symlinked files instead of truncating them correctly [8], and dirFS.ReadLink now returns relative paths in errors instead of absolute ones, matching the behavior of every other dirFS method [9]. The tooling updates also pulled in a tools vendor refresh via updatestd [7].
Action items
- → Pull tools/gopls with assembly support if you're working with cgo or blended codebases golang/tools [plan]
- → Update golang/net and verify HTTP/3 server timeout behavior if you're on the bleeding edge golang/net [monitor]
- → Check gofmt behavior on symlinked files in your next vendor sync golang/go [monitor]
References
- [1] gopls: add CompiledAsmFiles in cache.Package golang/tools
- [2] go.mod: update golang.org/x dependencies golang/tools
- [3] go.mod: update golang.org/x dependencies golang/benchmarks
- [4] go.mod: update golang.org/x dependencies golang/perf
- [5] internal/http3: implement server read and write deadlines golang/net
- [6] go.mod: update golang.org/x dependencies golang/net
- [7] cmd/fix: pull in CL 791660 golang/go
- [8] cmd/gofmt: correctly truncate symlinks instead of buggy mangling golang/go
- [9] os: rewrite PathError.Path in dirFS.ReadLink to relative name golang/go
FAQ
- What changed in Go on July 9, 2026?
- The Go toolchain just got smarter about assembly files, and a coordinated dependency update is rolling through every major repo simultaneously.
- What should Go teams do about it?
- Pull tools/gopls with assembly support if you're working with cgo or blended codebases • Update golang/net and verify HTTP/3 server timeout behavior if you're on the bleeding edge • Check gofmt behavior on symlinked files in your next vendor sync
- Which Go repositories shipped on July 9, 2026?
- golang/tools, golang/benchmarks, golang/perf, golang/net, golang/go