-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
cmd/go: go get (with GO111MODULE=on
) is not grabbing the newest version of my software
#32208
Comments
Also, |
Each different major version of a module has a different module path (see the section "adding a dependency on a new major version" in https://blog.golang.org/using-go-modules), so the command to add the latest v2 version of the module would be:
|
I see. thanks. I didn't know |
@gilgameshskytrooper It looks like you might have just updated your If so, note that the /v2 version of voiceittech/VoiceIt2-Go@1195039
You might want to try https://github.com/marwan-at-work/mod to make the needed changes automatically. |
GO111MODULE=on
) is not grabbing the newest version of my softwareGO111MODULE=on
) is not grabbing the newest version of my software
@thepudds Huh. You are right. Thanks for the tip |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
because the latest release on Github is v2.2.0
What did you see instead?
I guess this is pretty weird to me because the go module system worked fine until v1.2.1 (released Mar 19). Furthermore, we have minimal dependencies (the main library itself only uses the standard library, tests use testify).
The text was updated successfully, but these errors were encountered: