134 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-10-04
stories 1

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

vscode-go drops VS Code engines older than v1.110

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

The Go extension's engine floor moves to VS Code v1.110.0, so anyone still running a build older than March 2026 stops being a supported target.

extension/package.json: bump vscode engine to v1.110.0 golang/vscode-go

by Hongxiang Jiang

extension/package.json now declares a vscode engine of v1.110.0, with accompanying fixes for the incompatible API changes that bump exposed. v1.110 was chosen because @types/vscode does not ship for every VS Code release and vscode-go wants to cover roughly the past 180 days of editor releases, so the practical effect is that extension development and CI must now target the newer engine and types.

Quick answers

What shipped in Go on October 4, 2026?
The Go extension's engine floor moves to VS Code v1.110.0, so anyone still running a build older than March 2026 stops being a supported target. In total, 1 commits landed.
Who contributed to Go on October 4, 2026?
1 developer shipped this update, including Hongxiang Jiang.
What were the notable Go updates?
extension/package.json: bump vscode engine to v1.110.0.