GoLand 2026.1.4

GoLand 2026.1.4 just dropped — the latest bug-fix update for JetBrains' dedicated Go IDE. Let's break down what's fixed, what's improved, and whether you should update right now.

Performance Push

This maintenance release focuses on stability and squashing regressions introduced in the 2026.1 branch. The team resolved several issues affecting the debugger, code completion, and the integrated terminal. Indexing performance on large monorepos sees a modest improvement, with the background indexer consuming less CPU during idle periods.

Bug Bashes

• Debugger fixed — Resolved an issue where breakpoints in generic functions were sometimes skipped during step-through debugging
• Code completion — Fixed a regression where autocomplete for struct fields inside closures would not trigger correctly
• JavaScript debug — Addressed an error thrown when debugging mixed Go/JS projects in the embedded Web view
• Source maps — New option to disable source maps during JavaScript debugging, improving startup time for full-stack projects
• VCS — Fixed a crash when opening the Git log on repositories with a very large commit history

Toolchain Tweaks

GoLand 2026.1.4 ships with updated Go 1.26 support, including the latest standard library changes. The integrated gofmt and staticcheck integrations now correctly handle the new iter package idioms that became popular in Go 1.26. The LSP-backed code lens for test functions no longer duplicates entries when multiple build tags are active.

Upgrade at Your Own Pace

This is a point release — no breaking changes, no new major features. If you're on 2026.1.x, grab it from the Toolbox App or via the IDE's built-in updater. If you're on 2025.3 or earlier, consider moving to 2026.1 branch first to benefit from the broader feature set introduced in the initial 2026.1 release back in March.