docs: record 1.6.1 Zapstore publish (go zsp, inline signer gotcha)
This commit is contained in:
parent
0d04445bf3
commit
2d6ee43001
1 changed files with 7 additions and 0 deletions
|
|
@ -2089,6 +2089,13 @@ Rules:
|
|||
`SIGN_WITH="$(sed -n 's/^SIGN_WITH=//p' ~/.config/skatespots/zsp.env)"; export SIGN_WITH`.
|
||||
Complete non-interactive publish:
|
||||
`SIGN_WITH="$(sed -n 's/^SIGN_WITH=//p' ~/.config/skatespots/zsp.env)"; export SIGN_WITH; zsp publish --quiet zapstore.yaml`
|
||||
✅ **Published 1.6.1 on 2026-10-12** — the app's usual path is an **inline
|
||||
`SIGN_WITH=<nsec1…>`** (the value lives only in the shell/history, never in
|
||||
the repo); verify the signer is the app identity first (`nak key public` →
|
||||
`npub1yrnuj…` / hex `20e7c953…`). Use **`~/go/bin/zsp`** (v0.4.11) — the
|
||||
`zsp` on `PATH` (`~/.local/bin/zsp`) is older (v0.4.10). `zsp` warns that a
|
||||
nsec in env is insecure (prefer `bunker://`); the relay event to check is
|
||||
`nak req -k 30063 -d org.skatespots.app@<version> wss://relay.zapstore.dev`.
|
||||
|
||||
### Relay archive (dataset backup)
|
||||
- **Transfer content between keys (`scripts/transfer-content.mjs`, 2026-10-04):**
|
||||
|
|
|
|||
Loading…
Reference in a new issue