util.sh: regenerate go.sum to fix incorrect hash values #255
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
gomod-zip copied go's zip creation code but they had diverged.
due to this, gomod-zip created different zip files in the cache
compared to what go mod download would create (fixed in #254)
From Go 1.15.11 and Go 1.16.3, go automatically derives the ziphash
from the zip file in the cache - golang/go#44812.
This meant that go added incorrect hash values to go.sum because these
were derived from the zip files produced by the diverged gomod-zip code.
So remove go.sum here and regenerate again using go mod download and go mod tidy
to include the right hash values.
Note - this line should be removed after one clean publishing-bot run to be able to catch checksum
errors from
go mod download
in the future.Fixes broken publishing-bot. We get this error for component-base
release-1.21
now:Note -
go mod tidy
on the published component-base repo's master also produces a checksum error today./hold
/cc @sttts @dims @liggitt