x/pkgsite:

[halturin]

What is the URL of the page with the issue?

https://pkg.go.dev/github.com/ergo-services/ergo

What is your user agent?

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36

Screenshot

What did you do?

just visit the link above

What did you expect to see?

Correct version. The latest tag is v.2.0.0

What did you see instead?

Version: v1.2.7-0...-83c5934

[seankhliao]

The module hasn't declared the correct module name (/v2 suffix) in its go.mod

[ALTree]

Reading: https://go.dev/blog/v2-go-modules.

By definition, a new major version of a package is not backwards compatible with the previous version. This means a new major version of a module must have a different module path than the previous version.

[halturin]

@ALTree thanks for the link. It explains well, but it worst solution that could be made, IMHO.

[ALTree]

It's unpleasant indeed. Making it unpleasant to break backward-compatibility was one of the design goals:

Semantic import versioning is more work for authors of packages. They can't just decide to issue v2, walk away from v1, and leave users like Ugo to deal with the fallout. But authors who do that are hurting their users. It seems to me a good thing if the system makes it harder to hurt users and instead naturally steers authors toward behaviors that don't hurt users.

From the end of this, also linked in the blog post above.

[halturin]

I believe, any bad solutions/decisions have enough reasons/explanations why they were made.

It would be much better to have it as an option, but not to force use this way. that's the only making me crazy )

[halturin]

at least it shouldn't be a "must have" for the godoc.