New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 0.33.0 #2212
Comments
Hmm, I thought we don't use dlv-dap anymore. |
RC is available here - https://github.com/golang/vscode-go/releases/tag/v0.33.0-rc.2
Thanks! |
Change https://go.dev/cl/402634 mentions this issue: |
For go-outline, when I set Update: am not seeing this behavior again . Will file an issue if i notice it again. I don't think its related specifically to the go-outline, but with switching between all legacy and gopls. |
@suzmue nice finding - I think that is due to the issue described here #1896 (comment) I think. Gopls crashes during shutdown golang/go#52543 and leaves the extension in a broken state. Seems like any change that affects gopls makes this happen. It's a preexisting bug, but is much easier to hit if users play with the Go Explorer UI (experimental). Should we delay release until we have a workaround? |
For #2212 Change-Id: I6ce72a04c2e9b9b35acfad106b6f4744de9dad40 Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/402634 Reviewed-by: Polina Sokolova <polina@google.com> Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com> TryBot-Result: kokoro <noreply+kokoro@google.com>
We decided to hold off the release till early Monday. |
Release is out https://github.com/golang/vscode-go/releases/tag/v0.33.0 |
Change https://go.dev/cl/403474 mentions this issue: |
Release candidate (April 28, 2022)
master
for the releasegopls
CHANGELOG.md
release
for the releaserelease
for a pull requestmaster
to prepare for the releasepackage.json
from a-dev
suffixnpm install
to make surepackage-lock.json
is up-to-date$ tools/license.sh; mv LICENSE.prod LICENSE
)Final (May 1, 2022)
Prepare for the Next Release
master
post-releasemaster
branchpackage.json
package-lock.json
The text was updated successfully, but these errors were encountered: