-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Invalid github.com/go-delve/liner version #3025
Comments
Seems that after golang/go#51312 (comment) go does not treat branches with semantic-version names as releases. go.mod points now to github.com/go-delve/liner version v1.2.2-1 but is a branch name not tag; this causes go 1.18 errors like
Using default goproxy does not return error (maybe tag was cached before changes):
Please verify and fix. |
cc @derekparker you have to make a tag the module proxy and its consequences have been a disaster for cmd/go. |
To be precise, that behavior was changed for golang/go#35671, which was also backported to Go 1.16 and Go 1.17 as a minor security issue. |
delve/go.mod
Line 10 in 9c5777e
There is no v1.2.2-1 tag in
https://github.com/go-delve/liner/tags
The text was updated successfully, but these errors were encountered: