-
Notifications
You must be signed in to change notification settings - Fork 727
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
"go mod download" dirties go.sum #226
Comments
This might be related to golang/go#43994, and seems to be happening across multiple Go projects. |
Good find, thanks! So we can probably just call |
I think |
Thanks for finding this issue. Edit: The official Go documentation for go mode download -
I think we still need this for the unit test step that I highlighted above? In the CI, however, we need to check for duplicate/unused/missing dependencies.
This would be a new step in the workflow. |
According to golang/go#43994 go mod tidy should be used to prime the module cache. Updates #226
According to golang/go#43994 go mod tidy should be used to prime the module cache. Updates #226
According to golang/go#43994 go mod tidy should be used to prime the module cache. Updates #226
According to golang/go#43994 go mod tidy should be used to prime the module cache. Updates #226
Fixed by #232. |
This might be a problem with the Go toolchain, but I've not found a relevant bug yet.
Since d124590 I get the following (using go 1.16):
Running
go mod tidy
afterwards removes the entry again. This causes CI builds so (silently, due to another bug) fail.The text was updated successfully, but these errors were encountered: