Open wiardvanrij opened 2 years ago
Hey, thanks for reporting.
I assume you mean it does not work because the go
statement is still 1.15?
Yea, we don't change go statement version for compatibility. In practice this is never needed, unless you want to use potentially new commands in .mod
file which bingo does not sue. Why you want that go
version to be improved?
Well I just noticed it because I first checked the package on github and saw that they changed their mod file. I think it's "weird" or if anything, a little bit confusing to not exactly use the 'upstream' mod file. If you have a clean setup and use the bingo get
we do get the exact version. So that does not make it consistent.
I personally don't have a strong opinion about how it should work.
Just to be strict, exeat version of go
? Because that is simply version of Go module format nothing else (:
bingo version
output:v0.5.2
go version
output:go version go1.18 darwin/arm64
What happened:
I'm running with
bingo get github.com/plexsystems/promdoc@v0.7.0
which looks like:
Then I did the update with:
bingo get github.com/plexsystems/promdoc@v0.8.0
and I got:
What you expected to happen:
Getting:
How to reproduce it (as minimally and precisely as possible):
already described
Logs (use
bingo get -v <thing you do>
for verbose output):Anything else we need to know:
I fixed this by removing {package}.mod (in this case promdoc.mod and then run the get on v.0.8.0