can not upgrade to v1.9.1

[parsibox]

hi
i use windows 11 64 bit and go 1.24 i can not update to v1.9.1

go: -d flag is deprecated. -d=true is a no-op
go: downloading github.com/go-sql-driver/mysqlc
go: github.com/go-sql-driver/mysql@v1.9.1: verifying module: checksum mismatch
	downloaded: h1:oDr3crteKcueQ18yeWSyj52l3Qp8kh4zQlbbJFq0hLY=
	sum.golang.org: h1:FrjNGn/BsJQjVRuSa8CBrM5BWA9BWoXXat3KrtSb/iI=

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'.

[methane]

how can I reproduce the error?
On my machine, go mod init test1; go get github.com/go-sql-driver/mysql@v1.9.1 works fine.

[methane]

When I released v1.9.1, I made a mistake and tagged the wrong commit first, then immediately tagged the correct commit to overwrite it.
I don't think it was even a minute in between, but there is a possibility that it was cached somewhere during that time.

The correct hash value is registered in sum.golang.org. Could you try running go clean -modcache and then go get?

If that doesn't solve the error, the wrong cache may be on a proxy server somewhere, not on your machine.
Are you using any caching proxy servers?

[xmx]

me too

[methane]

@xmx Have you read my comment above? I am waiting additional information. Just "me too" isn't helpful.

[xmx]

As you mentioned, I was using the https://goproxy.io proxy server. When I switched to https://goproxy.cn, the issue was resolved.

[shogo82148]

It seems certain proxies have cached an incorrect commit. This is not a healthy situation.
How about releasing v1.9.2 with exactly the same contents as v1.9.1?

[methane]

done