Closed hookenz closed 3 years ago
Hi. For whatever reason, the tagging of that version messed up and it looks like the cached version is corrupted. Fortunately, there's newer versions so please try wails update
.
Hi. For whatever reason, the tagging of that version messed up and it looks like the cached version is corrupted. Fortunately, there's newer versions so please try
wails update
.
Thanks for the prompt reply. That seems to have fixed it. Why didn't it fetch the latest version at the beginning?
What do you mean? It installs the latest for me:
lea@192-168-1-105 /tmp % go get github.com/wailsapp/wails/cmd/wails
go: found github.com/wailsapp/wails/cmd/wails in github.com/wailsapp/wails v1.9.1
After go get. First time I'd ever tried it. Might have been a go get anomaly. Thanks for replying
I'd like to clarify that go get
installed v1.8.1 for me too, however when checking the tags in the downloaded repo, v1.9.1 is also there:
joe@jabberwocky ~/g/s/g/w/wails (master)> git describe --tags
v1.8.0-16-g0c2c56e
joe@jabberwocky ~/g/s/g/w/wails (master)> git tag | tail -1
v1.9.1
Tested on Manjaro and two Debian VMs (one of which had a fresh Go installation)
Really weird, considering that https://proxy.golang.org/github.com/wailsapp/wails/@v/list also lists v1.9.1 as latest.
go get is often incredibly weird when it comes to versioning
Thanks for that insight @jozsefsallai ! There was a bug a while back with the Semver package from masterminds which messed up after a .9 minor version but I don't think that's it.
I wonder if go get only gets the latest tag on master rather than across the repo. Unlikely?
Description Installed wails for the first time on windows machine. Ran wails init and it failed
To Reproduce
Expected behaviour It should have produced a suitable starter project but didn't
System Details
Additional context None