v0.41.2

[hyangah]

Release candidate

• Announce the release, leave enough time for teams to surface any last minute issues that need to get in before freeze. Make sure debugger and gopls teams are looped in as well.
• Check the milestone and resolve/move unresolved issues.
• Update release for the release
  • Create a branch against release for a pull request.
  • Merge changes from master to prepare for the release.
  • Change the version in package.json from a -dev suffix
  • Run npm install to make sure package-lock.json is up-to-date
• Check the Long Tests status is green. Otherwise, fix the tests, send cls for review, submit them, and repeat.
• Perform manual smoke tests
• Create new RC version tag for v0.41.2-rc.1 at gerrit’s vscode-go repo management page
  • Go to the release page https://github.com/golang/vscode-go/releases and check if the new release candidate is up. If necessary, you can manually edit the comment by clicking the “Edit” button. Don’t mutate uploaded vsix.
  • Ask @golang/tools-team and contributors to this release to test the release candidate

Final (March 14, 2024)

• Tag the new release for v0.41.2
• Monitor the cloud build status
• Update the release description with CHANGELOG contents
• Close the milestone

[gopherbot]

Change https://go.dev/cl/571098 mentions this issue: extension/CHANGELOG.md: mention user-visible fixes