cmd/go, x/mod: "invalid go version" message mentions old version format

[dominikh]

When parsing an invalid go line in a go.mod, the error message says

go: errors parsing go.mod:
go.mod:3: invalid go version '1.22foo': must match format 1.23

but that's not strictly true, it doesn't have to match the 1.23 format anymore.

[seankhliao]

cc @bcmills

[jamietanna]

What version of the go CLI was this with? I've hit this this morning when using gopls that's been compiled with a pre-1.21 go. The solution was to upgrade go.

[vincenthsh]

just came across this, to update vscode go tooling:

1. Press Ctrl+Shift+P
2. Select Go: Install/Update tools

or just to update golang language server:

go install golang.org/x/tools/gopls@latest

and you may Ctrl+Shift+P to restart language server

[gopherbot]

Change https://go.dev/cl/527897 mentions this issue: modfile: use new go version string format in error message

[amrojjeh]

I just got this error message recently after I updated go. I updated gopls as well and that did not fix it. For now I've manually edited the version number to be 1.21 rather than 1.21.1

[optik-aper]

I am also noticing this occurring in newly go mod init'd projects on fresh pull of gopls@latest. Manually editing the go version in go.mod allows the language server to restart without error. I'm using vim-go which utilizes YouCompleteMe for the LSP communication to gopls.

go version                                                                                             
go version go1.21.0 linux/amd64

gopls version                                                                                         
golang.org/x/tools/gopls v0.13.2
    golang.org/x/tools/gopls@v0.13.2 h1:Pyvx6MKvatbX3zzZmdGiFRfQZl0ohPlt2sFxO/5j6Ro=

[Seefooo]

I am also running into this. Similar setup to @optik-aper:

go version go1.21.1 linux/amd64
golang.org/x/tools/gopls v0.13.2
    golang.org/x/tools/gopls@v0.13.2 h1:Pyvx6MKvatbX3zzZmdGiFRfQZl0ohPlt2sFxO/5j6Ro=

[andydotxyz]

Possibly related to #63370?
There seems to be confusion to what version numbers the tools should support. Part of the challenge of introducing a new format and requiring it in the same release I think?

[let4be]

For me fixing version in go.mod and go.work to 1.21 didn't resolve the issue :(
What am I missing?

[let4be]

Hrm... should do this for all other modules in a workspace as well
Okay, changing all stuff to 1.21 resolved the issue

Is there currenlt no way to specify the version exactly, like 1.21.3?

[oussamaAbdelwahed]

just came across this, to update vscode go tooling:

1. Press Ctrl+Shift+P
2. Select Go: Install/Update tools

or just to update golang language server:

go install golang.org/x/tools/gopls@latest

and you may Ctrl+Shift+P to restart language server

After doing the steps above , you sometimes have to manually close and reopen vscode (even Ctrl+Shift+P then 'Reload Window' doesnt worked for me )

[MeanManMachineMan]

Sorry to bump and old thread but there's another way to go around it since in my case even a language server restart didn't fix the issue. Instead of forcing gopls version updates, i saw that my vscode itself was using an older go binary (which could very well be why the solution wasn't working for me). I personally use and recommend gvm for managing multiple go versions so i thought of using the path that is specified by gvm for go1.21.5 and forcing vscode to use that. Step by step:

1. Run gvm use go1.21.5 or whichever version you want, then echo $GOROOT:

 [-> echo $GOROOT
 /Users/your_username/.gvm/gos/go1.21.5

2. From the bottom right of the vscode window, select the go version -> Choose Go Environment -> Choose from file browser. Hit Cmd+Shift+. to be able to view hidden folders in the file explorer and then locate the path above. Navigate to bin->go and select that file.
3. Follow the vscode prompt to recompile gopls and other modules with this version and it will automatically restart the language server after that.