Hey thanks! i'm no longer signing 0xchat. Tor browser is a web update which is in alpha, so running those when I remember, for now
hi nostr:nprofile1qqs8y6s7ycwvv36xwn5zsh3e2xemkyumaxnh85dv7jwus6xmscdpcygpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz8thwden5te0dehhxarj9ekh2arfdeuhwctvd3jhgtnrdakj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qxvpy4 spotted tor-browser outdated in zap.store from some days, even this time with a critical vulnerability pending, and 0xchat nostr:nprofile1qqs84k6jpsav0jmdeqjn2zxlpnsajaw6f8l0m2d4e9t8gjsyn53s4nspzemhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6qgdwaehxw309aukzcn49ekk2qghwaehxw309aex2mrp0yh8x6tpd4ehgu3wvdhk6pw0r8j still at 1.3.4 🫡
Discussion
Hey, I’ve signed 0xChat v1.3.5, but it seems that the version on Zap Store is still v1.3.4. Could you help check it?
Confirm the problem, I also still see v1.3.4 in zap.store
I see the 1.3.5 release event is in the relay, and it has the exact same created_at as 1.3.4 (created_at: 1727661888), that is strange. I think the UI is seeing 1.3.4 as latest for that reason. Might be a bug in the CLI. Can you share which exact CLI version you are using? I don't see a zapstore.yaml in the root of your project, are you pulling from Github or uploading the artifact? Thanks!
I used v0.1.0, pulled from GitHub