Consider retract for v2 lineage

[nelz9999]

As of Go 1.16, there is now a retract directive in the module system.

From my quick-ish reading of things (https://go.dev/ref/mod#go-mod-file-retract), it seems that maybe the way to make end-users' lives a little easier is to publish a v2.0.1 with something like the following in the go.mod file:

retract (
    v2.0.0 // Published accidentally.
    v2.0.1 // Contains retractions only.
)

[nelz9999]

May solve some of this issues as mentioned on #440 ?

[stevenh]

Interesting, as v2.0.0 was never published via gomod it's still flagged as incompatible so shouldn't be considered.

If we did a v2.0.1 I would be concerned it would make the problem worse.

Is this something you have experience with @nelz9999 ?

[nelz9999]

Sorry to say that I don't have direct experience with this. 😢

But I know that this project fields requests in this realm fairly frequently, so I thought I'd mention the new directive in case it might help.

[stevenh]

Thanks I’ll ask on go nuts to see if this would solve the issue

[stevenh]

@nelz9999 what do you recon to merging #590 and tagging it v1.8.7?

It's not 100% clear if that will work, might need a v2.0.1, but I don't think it will do any harm?

[nelz9999]

@stevenh It might be worth a shot... It seems like it could be a low-risk experiment.

But my reading of the documentation has me thinking that you have to roll forward to retract behind you.

[nelz9999]

The new version must be higher than other release or pre-release versions; that is, the @latest version query should resolve to the new version before retractions are considered.

[stevenh]

So sounds like I need to tag v2.0.1 which can be incompatible.

[stevenh]

Feedback on gonuts indicated that was only needed for compatible versions as they are contained in different paths.

Given that I just tried with v1.8.7 and it seems to have worked, with the output from go list -m -versions github.com/gomodule/redigo reporting correctly:

github.com/gomodule/redigo 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 v1.8.7

So fingers crossed this works for all, thanks for raising the issue which lead to this :)