Closed thetillhoff closed 3 months ago
how are you determining that the second command installs a v1 version?
I ran go install github.com/thetillhoff/webscan/v3@latest
locally.
But now that you mentioned it, I tried running it in a golang:1.23
container and it installs the actual latest version there.
Seems to be a local problem... Sorry for the inconvenience, I'll close this issue.
Problem
When I run
go install github.com/thetillhoff/webscan/v3@latest
it installs an old v1 version instead of the latest v3.0.2 version. How do I resolve this?Context
Yesterday, I published a new major version (v3) and announced it to a small group of friends to try it out. One of my peers tried to install it with
go install github.com/thetillhoff/webscan@latest
, which failed withchecksum mismatch
.So I dove into the docs and learned the module path should be adjusted with each major version and did that by publishing a new patch-version.
Now the
go install
works, both for specifying the newest version withgo install github.com/thetillhoff/webscan/v3@v3.0.2
andgo install github.com/thetillhoff/webscan/v3@latest
. But the second command installs an old v1 version instead of the latest.How can I best resolve this?
Afaik noone uses it so far, so if I break backwards compatibility or it's unavailable for a bit it's not a problem for me.
The source code can be found at https://github.com/thetillhoff/webscan.