There are no tagged v0 or v1 versions of go-systemd. The versions of, for example, v22, are available at https://proxy.golang.org/github.com/coreos/go-systemd/v22/@v/list.

This is how the proxy protocol works; there is no easy way to discover what major versions of a given module exist.

@heschik shouldn't the v2-v20 versions be listed with +incompatible?

No. They are appropriately tagged and named in their go.mod files, so they aren't +incompatible.

Everything you're describing is working as intended, and the Go project doesn't use the issue tracker for questions, so I'm going to close this issue. See https://github.com/golang/go/wiki/Questions for where to ask further. #modules on the Gophers Slack would be a good place.

@heschik v1-v20 do not contain a go.mod file.

My mistake. There is no tagged major version 20; there is a tag v20 but that is an invalid semver tag and ignored by the Go command. Still working as intended, though.

I see. I was under the impression that the tag format wasn't as strict. Sorry for the noise!