Release 0.39.1

v0.39.1 - 17 Jul, 2023

This is a point release to update the link for the upcoming Go developer survey.
A list of changes can be found in the full commit history.

Release 0.39.1-rc.1

[release] prepare v0.39.1 release

3eafcb48 CHANGELOG.md: update for v0.39.1
9e7f8580 src/goDeveloperSurvey: update survey link and dates
75770e1f package.json: add gopls.start_debugging
5f5a8752 build/Dockerfile: skip global typescript, vsce installation
0de0e113 build: remove unused, outdated cloudbuild config
3b2da9a1 package.json: prepare for the v0.40.0 dev cycle
fb1dce6d package.json: align snippetsPreventQuickSuggestions with VS Code default

Change-Id: I9e1f5d40b5128c4c829850139aef92d26c18907f

Release 0.39.0

v0.39.0 - 12 Jun, 2023

We are in the process of removing legacy language features that were replaced by gopls since early 2021. The versions released after September 2023 will no longer offer features like code completion, navigation, documentation, formatting, and refactoring if the language server is disabled. In this release, we are showing deprecation notification messages if you are using the legacy language features. (Issue 2799)

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

Changes

• Added the go.showWelcome setting that controls whether to show the Welcome page. (PR 2704)

• Report when go.toolsManagement.go setting is invalid and ignored. (Issue 2753)

• Removed go.languageServerExperimentalFeatures setting which was deprecated in v0.21.0. (Issue 1109)

• Deprecated settings that affect only legacy language features and tools. They will be removed in the release after September 2023. (Issue 2799)

• "Go: Update/Install Tools" will install the latest version of golangci-lint instead of a vetted, pinned version. The extension chose to pin the versions of third-party go tools it installs in order to manage version skew and reduce security risks. However, golangci-lint is frequently released and its community is active enough to handle compatibility/security issues. We decided to install the latest version by default. (Issue 2763, 2485)

• Debug: show error when the process picker is hidden (CL 499601). To learn more about the process picker in debug, see Launch.json "processId" documentation.

• Debug: args attribute now accepts a string typed value. The argument string is parsed into word arguments with rules similar to bash except that there is no shell expansion. This change allows to use vscode variables like ${input:args}. (Issue 2621)

• The extension no longer caches PATH environment variable, which helps interoperate with extensions that modify PATH. (Issue 2617)

• Updated LSP to v3.17.3 and VS Code language client library to v8.1.0. This includes fixes for request ordering issues around full document sync and bugs around shutdown.

• Replaced the extension user survey link to https://go.dev/s/ide-hats-survey. (CL 497536)

• Updated settings to sync with gopls@v0.12.

• Third-party go tools dependencies: use gofumpt@v0.5.0 and revive@v1.3.2 and install staticcheck@v0.3.3 when building with go1.18 or older.

Delopment process updates

• Updated @vscode/vsce version to address the xml2js prototype pollution vulnerability report

Documentation

• Debugging documentation includes tips for debugging with -trimpath. (Issue 2609)
• Added advanced semantic syntax highlighting options. (Issue 2682)

Thanks

• Thank you for your contribution, @fflewddur, @ZekeLu, @cuining, @weikanglim, @niklaskorz, @xmmak, @jamalc, @suzmue, @hyangah!

Release 0.39.0-rc.1

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

• Commits: v0.38.0...v0.39.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.38.0

v0.38.0 - 28 Feb, 2023

This release adds default go tasks to help build and test your Go projects.

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

Changes

• Added default go task provider (Issue 194)
• Updated pinned golangci-lint version to fix memory leak issue with Go 1.20 (Issue 2654)
• gopls releases will now have a staged rollout in VS Code (CL 468497)
• Added extension keywords to make this extension easier to find in the VS Code Extension Marketplace (Issue 2657)
• Deleted the broken references codelens code (Issue 2519)
• Added support to handle missing variables in legacy debug adapter gracefully (Issue 2397)

Development process updates

• Upgraded esbuild to support s390x (Issue 2668)
• Use --profile-temp for testing with clean env (Issue 2458)

Thanks

Thank you for your contribution, @ankon, @hyangah, @jamalc, and @suzmue!

Release 0.38.0-rc.3

.github/workflows: fix release.yml to use npx vsce for packaging

Updates golang/vscode-go#2676

Change-Id: Idba55e5976bf85e587a4cef04773c15114446087
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/470975
Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com>
TryBot-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Suzy Mueller <suzmue@golang.org>
(cherry picked from commit dde5592e3d5a3825cc9a68b7d7268c672d4c319a)
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/471036
Run-TryBot: Suzy Mueller <suzmue@golang.org>
Reviewed-by: Jamal Carvalho <jamal@golang.org>

Release 0.37.1

v0.37.1 - 17 Jan, 2023

Fixes

• Fixed spurious file creation bugs on branch switches. (Issue 2570)

Changes

• Added promotion for the annual Go developer survey (2023 Winter).

Thanks

Thank you for your contribution, @suzmue!

Release 0.37.1-rc.2

[release] src/goDeveloperSurvey: drop extra " from message

Change-Id: I3badc68ee7b9c983ee70a836173accc794d4c913
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/462475
TryBot-Result: kokoro <noreply+kokoro@google.com>
Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com>
Reviewed-by: Robert Findley <rfindley@google.com>

Release 0.37.1-rc.1

[release] prepare v0.37.1

Updates golang/vscode-go#2614

Change-Id: I8c24ec7d0666c072fc91379520d8d0240bf7d13f
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/462379
Reviewed-by: Robert Findley <rfindley@google.com>
Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com>
TryBot-Result: kokoro <noreply+kokoro@google.com>

Release 0.37.0

v0.37.0 - 19 Dec, 2022

This release includes new static analysis features that report known vulnerabilities in your dependencies. These vulncheck analysis tools are backed by Go's vulnerability database and the Go language server's integration of govulncheck.
Read Go's support for vulnerability management to learn about the Go team's approach to helping Go developers secure their open-source dependencies.

vulncheck.mp4

Changes

• The new "Go: Toggle Vulncheck" command enables/disables imports-based vulnerability analysis. This requires gopls v0.11.0 or newer.
• Test and debug test code lenses are added to some subtests if the test names can be determined. (Issue 2536)
• Gopls settings was updated to match gopls@v0.11.0.
• "go.formatTool" setting accepts a special value "custom", which causes the extension to use the custom formatter configured with the setting "go.alternateTools": { "customFormatter": <your custom tool name> }. (Issue 2503)
• The experimental "Go: Run Vulncheck (exp)" command was removed.
• The extension no longer bypasses Delve's Go version check by default. Users must install the delve version compatible with their Go version, or explicitly configure their launch configuration to pass the --check-go-version=false flag using the dlvFlags attribute. (Go Delve Issue 3058)

Fixes

• The editor survey prompt logic was adjusted for uniform sampling. (Issue 2545)
• Fixed the crash bug when handling coverage profiles involving go //line-directive. (Issue 2453)
• Updated dependencies to address CVE-2022-37603 and CVE-2022-24999.

Thanks

Thank you for your contribution, @devuo, @pjweinbgo, @aarzilli, @tklauser, @hyangah, @suzmue, @jamalc!