go-sqlite3: Retract "Incompatible versions" of this package

@martinrode, when you run go get github.com/mattn/go-sqlite3@v1.14.15, it will downgrade other dependencies that require higher versions of that module until no higher version is required.

If you just want to lop out those parts of the dependency graph, you can use an exclude directive:

go mod edit -exclude=github.com/mattn/go-sqlite3@v2.0.3+incompatible

If you exclude all of the versions that have higher SemVer precedence than the version you do want, then go get will be able to select that version without performing other downgrades.

@rittneje

Curiously, I would have expected issues due to v2.0.4 through v2.0.6, as these have go.mod files and thus are not +incompatible. However, they don’t have a v2 folder so are still partially incompatible. That may be why they don’t even show up on pkg.go.dev.

Yeah, I guess that for v2.0.4 - v2.0.6 to be shown up on pkg.go.dev, some works will be required: https://blog.golang.org/v2-go-modules

---

@mattn

Unfortunately, no way to remove version on Go module index server. https://index.golang.org/

@rittneje

it is unclear from the description of retract whether you can retract +incompatible versions.

I did some tests on https://play-with-go.dev/retract-module-versions_go116_en/ , and it seems that +incompatible versions can be retracted.

---

$ git tag
v1.14.8
v2.0.0
v2.1.0

$ git log
commit bcb92f95c4364d7514ba83942c4a752854891d42 (HEAD -> main, tag: v1.14.8, origin/main)
Author: Random Gopher <gopher@gopher.com>
Date:   Wed Aug 4 06:04:32 2021 +0000

    Fix severe error in Go proverb

commit a39f79d0990a9555f0d628c0a03c3c9e8214c62a (tag: v2.1.0)
Author: Random Gopher <gopher@gopher.com>
Date:   Wed Aug 4 06:01:14 2021 +0000

    Switch Go proverb to something more famous

commit 55c9e7421a031751b8977709be0fdc1c16b905a7 (tag: v2.0.0)
Author: Random Gopher <gopher@gopher.com>
Date:   Wed Aug 4 06:00:01 2021 +0000

    Initial commit

→ In here, you can see that I tagged v2.0.0 first, and then v2.1.0, and then v1.14.8 for the last.

$ cat go.mod
module gopher.live/u9eedb79bfe02/proverb

go 1.16

// Go proverb was totally wrong
retract v2.1.0

→ In here, you can see that I retracted v2.1.0 by writing retract v2.1.0 in go.mod.

$ go list -m -versions gopher.live/u9eedb79bfe02/proverb
gopher.live/u9eedb79bfe02/proverb v1.14.8 v2.0.0+incompatible

$ go list -m -versions -retracted gopher.live/u9eedb79bfe02/proverb
gopher.live/u9eedb79bfe02/proverb v1.14.8 v2.0.0+incompatible v2.1.0+incompatible

→ In here, you can see that v2.1.0+incompatible is retracted.

---

So, my suggestion for the go.mod is:

module github.com/mattn/go-sqlite3

go 1.16

retract (
	v2.0.3
	v2.0.2
	v2.0.1
	v2.0.0
)

In addition to retracting a module, it is possible to deprecate it: https://golang.org/ref/mod#go-mod-file-grammar, “Deprecation” sub-header.

I think the ideal solution could be:

1. Release v2.0.7 that both deprecates this major version in favor of v1, and retracts v2.0.0-v2.0.7.
2. Release the next minor or patch release of v1 that retracts v2.0.0-v2.0.7.