The package to be published is tagged this way: git tag -a '1.0.0' -m 'First version' and git push --follow-tags origin … On github, I’ve published a release from that 1.0.0 tag.
Now, in the tool that should use the tool, I do: go get github.com/MYUSER/MYPACKAGE
The output shows this: go: added github.com/MYUSER/MYPACKAGE v0.0.0-20240401010128-eac52ef19ef8
The require section of go.mod shows the same
It’s as if GO ignores the actual tag/release. If I check in my GOROOT ($HOME/go/pkg/mod/github.com/MYUSER/), MYPKG is obviously downloaded there, with the same bogus version number
Same problem, different package I’m trying to publish:
You see, the release IS THERE.
I add the following line to go.mod: github.com/jeanfrancoisgratton/helperFunctions v1.0.0
Then run go mod tidy, and it then complains this way:
github.com/stretchr/testify/assert: github.com/jeanfrancoisgratton/helperFunctions@v1.0.0: verifying go.mod: github.com/jeanfrancoisgratton/helperFunctions@v1.0.0/go.mod: reading https://sum.golang.org/lookup/github.com/jeanfrancoisgratton/helper!functions@v1.0.0: 404 Not Found
server response: not found: github.com/jeanfrancoisgratton/helperFunctions@v1.0.0: invalid version: unknown revision v1.0.0