Closed Meroje closed 1 year ago
I guess you'll have to publish a new version anyway because of the l6
typo ? https://github.com/uber-go/dig/blob/cdbd7eb028bf80d536d4768330d7b471e03a078c/CHANGELOG.md#L18
INFO[9:17AM]: go.uber.org/dig@v1.16.0: verifying module: checksum mismatch
downloaded: h1:UvbC1KUaQKx6MQTALcKanqRuPQRX7Tnt1iIYZHH2shk=
sum.golang.org: h1:O48QoUEj4ePocypAIE5jz+SrxVdG/izHM1CZ/Yjrwww=
As v1.16.1 was released this can be closed because moving forward dig is installable again (event though v1.16.0 will remain "broken")
go: downloading go.uber.org/dig v1.16.0 go.uber.org/fx imports go.uber.org/dig: go.uber.org/dig@v1.16.0: verifying module: checksum mismatch downloaded: h1:UvbC1KUaQKx6MQTALcKanqRuPQRX7Tnt1iIYZHH2shk= sum.golang.org: h1:O48QoUEj4ePocypAIE5jz+SrxVdG/izHM1CZ/Yjrwww=
Seeing as the issue has been fixed in 1.16.1, perhaps we can retract 1.16.0.
@sywhang @r-hang what do you think about retracting the bad release to prevent this issue? https://go.dev/ref/mod#go-mod-file-retract
Describe the bug The current v1.16.0 version cannot be downloaded directly or from another proxy than
proxy.golang.org
while also verifying the sum.edit: the info file says it got this commit https://github.com/uber-go/dig/commit/7e2722294255db2818d377360e864bb6534e7812
To Reproduce
Expected behavior It should work, regardless of the GOPROXY value.
Additional context I guess the tag has been moved after publication but not before it was cached by the proxy ?