One of the golang packages I maintain redigo had a v2.0.0 tag created before the introduction of go mod and this still causes challenges today.
A kind soul pointed <https://github.com/gomodule/redigo/issues/585> out go mod retract <https://go.dev/ref/mod#go-mod-file-retract> the other day in the hope that this could help solve the problem. From what I've read it does seem like this is the case and that creating a v2.0.1 tag which includes retract ( v2.0.0 // Published accidentally. v2.0.1 // Contains retractions only. ) To be clear the go mod compatible structure of v2.0.0 was never created hence v2.0.0 is listed as incompatible e.g. go list -m -versions github.com/gomodule/redigo v0.0.0-do-not-use v1.7.0 v1.7.1 v1.7.2 v1.8.0 v1.8.1 v1.8.2 v1.8.3 v1.8.4 v1.8.5 v1.8.6 v2.0.0+incompatible This could help but my concern is if this doesn't work it could make matters worse, so wanted to see if anyone could advise on this process? Regards Steve -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAHEMsqaXKVNCYXja7GbKhOp7UvH2J3TBpyZe4r%3DB92wbFhVyCw%40mail.gmail.com.
