GoLand 2026.2.1

I upgraded GoLand to 2026.2.1 (build 262.9437.195) the day it dropped — August 10, 2026 — so you don't have to. Verdict up front: if you're on 2026.2, take the patch. It's small, it's safe, and it fixes things you will hit eventually. If you're still on 2026.1, this isn't the release that forces your hand.

The Worth-It Fix

The standout change is under Profilers: the Escape Analysis Tool no longer fails to compile when a profile contains <autogenerated> entries on Windows or WSL2. That's a niche-sounding bug, but it's the kind of thing that eats an afternoon when you're chasing an allocation hotspot in a generated-code-heavy codebase. Fixed here.

Go Fix Goes Pre-Commit

GoLand now wires the go fix action into the pre-commit check, with a small visual tweak to how the suggestion renders. One cosmetic wrinkle remains: Go fixes with no quick fix attached show no preview in the inspection popup — minor, but noticeable if you live in that panel.

What Else Landed

• The Go SDK notification wording was cleaned up (less alarmist).
• Figma Connect picked up a batch of polish: a "set up Figma skill" flow, drag-a-node-to-terminal support that inserts the node id, and fixes for the double confirmation dialog on RemDev startup and the retry banner flapping between green and yellow states.
• Ruby projects no longer get false "Cannot resolve" warnings on bare CSS imports.
• TypeScript LSP handling was decoupled from LSP client caches, which should stabilize inlay hints in mixed-language files.

Should You Update?

Yes — but it's a low-urgency yes. The Escape Analysis fix is the only one with real teeth for most Go developers, and it only matters on Windows/WSL2. If you work on macOS or Linux and never touch profiling, you can wait for the next feature release. Everyone else: grab it from the Toolbox App and move on with your day.