Release 0.34.1

v0.34.1 - 30 June, 2022

A list of all issues and changes can be found in the v0.34.1 milestone and commit history.

Bug Fix

• Fixed (Issue 2300) that prevented the extension from complete activation when the language server fails to start.

Thanks

Thank you for your contribution, @jamalc, @hyangh!

Release 0.34.1-rc.2

• Milestone: https://github.com/golang/vscode-go/issues?q=milestone%3Av0.34.1

• Commits: v0.34.0...v0.34.1-rc.1

• How to test prerelease

  • Download the .vsix file from this Releases page.
  • Navigate to the Extensions view in VS Code (Ctrl+Shift+X). Click on the "..." in the top-right corner, select "Install from VSIX", and select the .vsix file you downloaded. Alternatively, you can run code --install-extension Go-latest.vsix or open the Command Palette and run the "Extensions: Install from VSIX..." command.
  • If prompted, reload VS Code.

Release 0.34.0

v0.34.0 - 22 June, 2022

This release adds support for LSP 3.17 and requires Visual Studio Code 1.67+.

Features

This release includes improvements to the Go: Run Vulncheck (Experimental) command (Issue 2185, 2186, 2214). Use it to find security issues in your dependencies.

Documentation

Documentation for vscode-go can now be found on the wiki (Issue 2094).

Thanks @thediveo for updating the debugging documentation!

Bug Fixes

TestMain(m *testing.M) is no longer treated as a test (Issue 482, 2039)

Code Health

• Enabled strict type checking (Issue 57)
• Updated release notes generation script to improve release process automation
• Fixed bugs in testing

Thanks

Thank you for your contribution, @hyangah, @jamalc, @polinasok, @suzmue, @thediveo, and @dle8!

Release 0.34.0-rc.2

• Milestone: https://github.com/golang/vscode-go/issues?q=milestone%3Av0.34.0

• Commits: v0.33.1...v0.34.0-rc.2

• How to test prerelease

  • Download the .vsix file from this Releases page.
  • Navigate to the Extensions view in VS Code (Ctrl+Shift+X). Click on the "..." in the top-right corner, select "Install from VSIX", and select the .vsix file you downloaded. Alternatively, you can run code --install-extension Go-latest.vsix or open the Command Palette and run the "Extensions: Install from VSIX..." command.
  • If prompted, reload VS Code.

Release 0.34.0-rc.1

• Milestone: https://github.com/golang/vscode-go/issues?q=milestone%3Av0.34.0

• Commits: v0.33.1...v0.34.0-rc.1

• How to test prerelease

  • Download the .vsix file from this Releases page.
  • Navigate to the Extensions view in VS Code (Ctrl+Shift+X). Click on the "..." in the top-right corner, select "Install from VSIX", and select the .vsix file you downloaded. Alternatively, you can run code --install-extension Go-latest.vsix or open the Command Palette and run the "Extensions: Install from VSIX..." command.
  • If prompted, reload VS Code.

Release 0.33.1

v0.33.1 - 24 May, 2022

This is the last release that supports Visual Studio Code 1.66 or older.
We plan to add support for LSP 3.17 in the next release and the change requires Visual Studio Code 1.67+.

Changes

• Updated settings to be in sync with [email protected]. See the release note to learn new features like the //go:embed analyzer, and improved hover for imported packages.
• Prepared for 2022 mid-year Go developer survey.

Release 0.33.1-rc.1

• Milestone: https://github.com/golang/vscode-go/issues?q=milestone%3Av0.33.1

• Commits: v0.33.0...v0.33.1-rc.1

• How to test prerelease

  • Download the .vsix file from this Releases page.
  • Navigate to the Extensions view in VS Code (Ctrl+Shift+X). Click on the "..." in the top-right corner, select "Install from VSIX", and select the .vsix file you downloaded. Alternatively, you can run code --install-extension Go-latest.vsix or open the Command Palette and run the "Extensions: Install from VSIX..." command.
  • If prompted, reload VS Code.

Release 0.33.0

v0.33.0 - 1 May 2022

📣 Remote attach debugging is now available via Delve's native DAP implementation with Delve v1.7.3 or newer. It is now the default with the Go Nightly and will become the default for the stable releases in mid 2022.

Changes

• staticcheck: if go 1.16.x or older is used in installing tools, the extension chooses [email protected]. In order to use the latest version of staticcheck while working on projects that require older versions of go, you can utilize the "go.toolsManagement.go" setting to specify a newer version of go for tool installation. (Issue 2162)

• go-outline: go-outline is no longer required when gopls (v0.8.2+) is used.

• Activation: the extension defers commands and feature provider registrations until it runs go version and go env, and starts gopls. This change prevent the extension prematually export its features, but may result in a slight increase in extension activation time if those commands run slow.

• Survey: we show the Gopls opt-out survey prompt only when users change the setting to disable gopls.

• Test Explorer: fixed a bug in go.mod file parsing (Issue 2171)

• Debugging: we removed the informational popup at the start of remote attach session with dlv-dap. (Issue 2018)

Experimental features

This version includes two highly experimental features. They are still
in early stage and we are looking forward to hearing more user feedback.

• Go Explorer view: it displays environment variables and information about tools used by the extension. (Issue 2049)

goexplorer.1.mov

(Demo: Using the Go Explorer view UI to quickly change GOOS setup)

• Go: Run Vulncheck (Experimental) command: it runs the govulncheck command embedded in gopls, which identifies known vulnerabilities by call graph traversal and module dependency analysis. (Issue 2096)

Thanks

@jamalc, @polinasok, @dlipovetsky, @vladdoster, @suzmue, @hyangah

Release 0.32.0

v0.32.0 - 8 Mar, 2022

This version includes features to enhance Go 1.18 support. It works best when paired with the latest Go Language Server (gopls v0.8.0+) and Delve (dlv v1.8.0+).

Go 1.18 introduces substantial changes to the language spec, so many tools need rebuilding with Go 1.18 or newer. The extension now suggests updates of tools if it finds they were built with old versions of go which are inadequate for the version used for the project. If you opted in for auto-update, tools will be auto-updated.

In order to use Go 1.18, please follow the instruction to configure your Visual Studio Code to locate the right go binary, and run the Go tools using the "Go: Install/Update Tools" command.

A list of all issues and changes can be found in the v0.32.0 milestone and commit history.

Changes

• Starting with Go 1.18, the go command provides native support for multi-module workspaces, via go.work files. The new "Open 'go.work'" option in the Go status bar's quickpick menu allows users to access the corresponding go.work file.
  

• The extension no longer depends on gopkgs. Its use for "Go: Browse Packages" and "Go: Add Import" commands had been replaced with go list or commands in gopls. (Issue 258)

• The extension uses gopls instead of go-outline if gopls v0.8.0 or newer is used. We plan to complete the replacement work in the next release. (Issue 1020)

• The new "go.toolsManagement.go" setting allows users to specify the Go command for tools installation/updates separate from the Go command used for the project.

• The latest gopls requires go 1.13+ for installation, so the extension no longer asks for gopls updates when an older versions of go is used. (Issue 2030) Note gopls compiled with go 1.13 or newer can still process projects that use go 1.12. In case, you want to update gopls while working with an older version of Go, utilize the new "go.toolsManagement.go" setting.

• Reduced the verbosity of "Go: Locate Configured Go Tools" output.

Code Health

• Updated to [email protected] (CVE-2021-23566).
• Deflaked debug tests.
• Changed to check go.dev/dl instead of golang.org/dl for Go release.
• Improved documentation for the default formatting behavior and template support.

Thanks

@jamalc @suzmue @pavlelee @dekimsey @hyangah

Release 0.31.1

v0.31.1 - 8 Feb, 2022

A list of all issues and changes can be found in the v0.31.1 milestone and commit history.

Fixes

• Fixed the profile functionality broken by VSCode 1.63 (Issue 2048)
• Include fuzz tests in test explorer UI (Issue 2023)