Ugh I know what happened. I have ~/.cargo/bin/ngit too (that one is 0.0.1) - for some reason that one was loaded before in $PATH. But weird that loads the zs version (1.4.3) in other terminal session. So the zapstore cli is working correctly. I'll look at the publishing hanging issue
I wonder whether zapstore should check if the binary already exists in the path and warn the user about the conflict?
Please Login to reply.
Definitely! Will add as issue
I was going to do it for you but couldn't find you nostr git announcement ;-)
Also added as issue 🤣
