RepoJournal
Go @golang
167 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-05-29
stories 21
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

GO 1.27 RELEASE NOTES FINALIZED, TYPEPARAMS DEPRECATION BEGINS

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

Go 1.27 documentation shipped to x/website this morning with cleaned-up release notes, and the team is moving fast to deprecate legacy typeparams APIs before the next major version.

The release notes consolidation is complete [1] [2], with malformed net package links fixed [3] and documentation TODOs cleaned up [4]. This clears the decks for 1.27 RC1, which the team is preparing for with test infrastructure upgrades [5] [6]. Over in x/exp, typeparams aliases are being deprecated and inlined [7] to push users toward standard library equivalents, a migration path that will be codified with go fix after 1.27 ships and 1.26 becomes the minimum supported version. The copy builtin now correctly enforces that its first argument must never be nil [8], closing a type-checking gap that could have caused subtle runtime failures. Meanwhile, gopls is shipping targeted fixes: a new sql.Rows.Err analyzer [9] catches a common error handling bug, LSP client telemetry got more accurate [10], and a repro for a coherency violation in file caching was added [11]. Parser generation also got a critical fix: goyacc now uses math.MinInt16 instead of -1000 as a sentinel, which prevented it from handling large grammars where -1000 became a valid value [12].

Action items

References

  1. [1] doc/next: delete ↗ golang/go
  2. [2] _content/doc: add merged go1.27.md ↗ golang/website
  3. [3] doc: format net package release note ↗ golang/go
  4. [4] doc: inserted TODOs into 9-todo.md ↗ golang/go
  5. [5] internal/relui: unskip TestRelease/rc test ↗ golang/build
  6. [6] internal/relui: only run TestRelease/major on 1.26 and newer ↗ golang/build
  7. [7] typeparams: deprecate and inline aliased functions ↗ golang/exp
  8. [8] go/types, types2: first argument to copy must never be nil ↗ golang/go
  9. [9] go/analysis/passes/sqlrowserr: report missing sql.Rows.Err calls ↗ golang/tools
  10. [10] gopls/internal/server: add more LSP clients to telemetry mapping ↗ golang/tools
  11. [11] gopls/internal/test: add skipped repro for golang/go#64235 ↗ golang/tools
  12. [12] cmd/goyacc: use math.MinInt16 as sentinel value for large grammars ↗ golang/tools

$ ls golang/reviews/ # the step-back reads

the week in review FIPS 140 crypto fixes land across SHA-3, TLS 1.2, HKDF the month in review Go toolchain patches three CVEs as gopls hits v0.24.0
Full archive → Weekly reviews →

Quick answers

What shipped in Go on May 29, 2026?
Go 1.27 documentation shipped to x/website this morning with cleaned-up release notes, and the team is moving fast to deprecate legacy typeparams APIs before the next major version. In total, 21 commits landed.
What were the notable Go updates?
doc/next: delete, _content/doc: add merged go1.27.md, and doc: format net package release note.
♥

$ log @golang --recent

RISC-V Zfa assembly support, and a faster archsimd unifier 9 shipped Plan 9 Mkdir race fixed, riscv64 gets clobberdead mode 7 shipped gopls closes a CVE on dash-prefixed module paths, and the exp collections get a Set 52 shipped Compiler stops lifting unsafe.Pointer arithmetic 35 shipped

$ log --all # elsewhere on the wire

Agent Security Quiet day in agent security as guard coverage reaches four clients Alignment & Post-training verl defaults Ascend RL mode, open-instruct unblocks SFT packing

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.