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-06-18
stories 18
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

JSON V2 BREAKS INLINE TAG, ADOPTS EMBED INSTEAD

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

The encoding/json/v2 rewrite is renaming its `inline` tag option to `embed` to avoid conflicts with existing Go code that already uses `inline` for different purposes.

This is a breaking change for the v2 API, but necessary. Analysis of Go module proxies showed that existing code already uses the `inline` tag outside of encoding/json semantics [1]. The rename to `embed` aligns the JSON marshaling feature with Go's language-level embedding concept, making the semantic connection clearer. In parallel, the type system gained smarter function type inference for map keys [2], which will be critical for implementing generic composite literal inference. The compiler also got cleaner type renaming logic [3], consolidating dependent method renaming at the type level rather than scattering renames across individual methods and fields. Meanwhile, pkg.go.dev fixed a regression where local pkgsite instances weren't showing subdirectory package synopses [4], restoring feature parity with the production site. The ops desk shipped routine maintenance: pkgsite bumped to Go 1.26.4 [5], metrics updated x dependencies [6], and govulncheck fixed exit code propagation for wrapped errors [7].

Action items

References

  1. [1] encoding/json/v2: rename `inline` tag option as `embed` ↗ golang/go
  2. [2] go/types, types2: permit function type argument inference for map keys ↗ golang/go
  3. [3] cmd/compile: rename types with dependent methods instead of renaming methods ↗ golang/go
  4. [4] internal/{fetch,fetchdatasource}: populate subdirectory synopses ↗ golang/pkgsite
  5. [5] deploy: bump Go version to 1.26.4 ↗ golang/pkgsite
  6. [6] go.mod: update golang.org/x dependencies ↗ golang/pkgsite-metrics
  7. [7] cmd/govulncheck: fix exit code propagation for wrapped scan errors ↗ golang/vuln

$ 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 June 18, 2026?
The encoding/json/v2 rewrite is renaming its `inline` tag option to `embed` to avoid conflicts with existing Go code that already uses `inline` for different purposes. In total, 18 commits landed.
What were the notable Go updates?
encoding/json/v2: rename `inline` tag option as `embed`, go/types, types2: permit function type argument inference for map keys, and cmd/compile: rename types with dependent methods instead of renaming methods.
♥

$ 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.