-
Notifications
You must be signed in to change notification settings - Fork 18k
x/exp/cmd/gorelease: unexpected go.sum complaint #64051
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
Comments
what version of gorelease is this, and can you provide a reproducer? |
unfortunately, I haven't been able to get a sanitized reproduction outside our production code. This is still reproducing @latest (Nov 10, 2023). Has been since the Sep 5, 2023 release but the problem actually started reproducing when we bumped the version of go in this module from 1.18 to 1.20. And, yes, when we did so, we re-ran |
as a test, I tried installing all tagged versions of gorelease to see if it starts reproducing somewhere, and the behavior is present in all but the first release, which panics. |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
no longer reproducing in go1.21, but still does reproduce in go1.20 latest |
reproduced with go 1.22.9 with version v0.0.0-20241009180824-f66d83c29e7c |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
unknown (our organization is using go1.20.latest)
What operating system and processor architecture are you using (
go env
)?go env
Outputalso reproduces in linux
What did you do?
What did you expect to see?
normal output
What did you see instead?
There is actually nothing wrong with the go.sum file and re-generating it by deleting and re-running
go mod tidy
produces the same contents.The package builds just fine.
The text was updated successfully, but these errors were encountered: