Hi @roidelapluie, I haven't looked at the details here, but are you only placing your retract directives in versions with pre-release tags?

For example, v1.99.0-retract, v2.35.0-retract, and v0.35.0-rc1 are all semver pre-release tags:

9. A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version.

If you have only tried with pre-release tags so far, that might explain at least part of the issue.

From https://go.dev/ref/mod#go-mod-file-retract :

To retract a version, a module author should add a retract directive to go.mod, then publish a new version containing that directive. 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.

And also from the go mod ref, here is an explanation of what @latest means (including latest will not resolve to a pre-release tag once a non-pre-release tag is available, which makes sense as desirable behavior I think):

The string latest, which selects the highest available release version. If there are no release versions, latest selects the highest pre-release version. If there no tagged versions, latest selects a pseudo-version for the commit at the tip of the repository’s default branch.

I will try with a proper tag, thanks!

Thank you! That fixed the issue!!!! Awesome!