Closed roessland closed 1 year ago
Hi,
Unfortunately, I can't reproduce this bug as azure-sdk-for-go v65.0.0 has been released in the meantime and the actual bug has been resolved in this version.
According to this comment, you could use the environment variable GONOSUMDB as a workaround so, this should also work with go-mod-upgrade (note that I haven't tested it).
But I agree with you that go-mod-upgrade could in this case ignore the broken modules and allow to update the other modules. PR are always welcomed :smirk:
Closing this issue following the thumb up emoji. Feel free to reopen if needed.
Recently azure-sdk-for-go became too large for
go get
which causes a bunch of problems. v64.1.0 is the latest version below the size limit, and v64.2.0 is the latest version.It would be nice if go-mod-upgrade kept working and was able to update the other (non-broken) modules.