v4.0.0: Go get checksum does not match the one reported by checksum server.

[prestonvanloon]

🐞 Bug Report

Description

A tag for v4.0.0 was prematurely created for the release candidate 0 (v4.0.0-rc.0) and this was indexed by golang's checksum server and proxy. The tag for v4.0.0 was deleted and retagged later when the appropriate release candidate was promoted for release. As such, users are finding a checksum mismatch as the current v4.0.0 does not match that checksum that was previously issued.

The resolution for this is to create a new release from the same commit, v4.0.1 and allow golang to index that as the latest release.

Has this worked before in a previous version?

Yes

🔬 Minimal Reproduction

Use go get to fetch Prysm at v4.0.0

🔥 Error

    github.com/prysmaticlabs/prysm/v4/consensus-types/primitives: github.com/prysmaticlabs/prysm/v4@v4.0.0: verifying module: checksum mismatch
    downloaded: h1:BMMhPSzfYXQLxiweJY+hJEbmY/MI8ZShEbTz3omV3aY=
    sum.golang.org: h1:c7qkGB+iwiWRN00/29wQk37sG+XtsKjy0AGfpGHhaa4=

SECURITY ERROR
This download does NOT match the one reported by the checksum server.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.

🌍 Your Environment

Operating System:

  All

What version of Prysm are you running? (Which release)

  v4.0.0

Anything else relevant (validator index / public key)?

[prestonvanloon]

Fixed in v4.0.1 release
https://github.com/prysmaticlabs/prysm/releases/tag/v4.0.1