Server disk is at 99.8% capacity, it sounds like a good moment to migrate to our new Blossom server.
Updating DNS records for cdn.zapstore.dev now.
🤞
Github and web indexing are paused until widespread propagation. It will be resumed by the new indexing software, probably tomorrow.
godspeed.
Ah, I see.
Are we completely unable to push updates to zap store in the meantime?
Are you unable?
What zapstore CLI version are you on?
2.9.3 Still unable to push my release.
Run cd ./release # Navigate into the directory with assets
Publishing v0.6.0 to Zapstore using apksigner at /tmp/build-tools/android-13/apksigner...
Icon file: runstr_logo.png
APK file: runstr-0.6.0.apk
Notes file: release_notes.md
Checking APK signature...
✅ APK appears to be signed (found .RSA files)
Attempting to publish to Zapstore...
--- Zapstore Publish Output --- (0)
-------------------------------
✅ Successfully published version 0.6.0 to Zapstore!
I don't recognize that output at all. What tool are you using to publish?
That was from Github, I'm using cursor on windows.
I'm trying to understand which tool you used to create the app/release events sent to Zapstore. How did you publish? Or you just ask cursor to publish to zapstore?
Do you have zapstore CLI in your system?
Usually I just push to github and have a workflow that publishes to zap store from my main branch. Where do I download the CLI? I'm in an ubuntu wsl running curl -L https://zapstore.dev/download/zapstore-linux-amd64 -o zapstore but it doesnt seem to work.
That download link is not right. Where did you get it from?
Just checked https://github.com/HealthNoteLabs/Runstr/blob/main/.github/workflows/publish-zapstore.yml and got a headache.
I suggest giving https://zapstore.dev/docs/cli/publish/ to the agent, cross fingers and try again
Looking into running a custom selfhosted CDN right now. Are you using something like that or some SaaS? No judgment of course if it's the latter.
