release: 1.6.4 (crew chat sends with Amber no longer fail)

Fix: sending to a crew sequential-ised its per-recipient signer intents, so Amber
approvals land instead of timing out. Bump 1.6.3 -> 1.6.4, APK built + published
to Zapstore (verified on relay.zapstore.dev).
This commit is contained in:
SkateSpots 2026-10-13 00:10:12 +07:00
parent 27084a4e7b
commit 07d4df037d
4 changed files with 12 additions and 4 deletions

View file

@ -2143,7 +2143,7 @@ Rules:
`SIGN_WITH="$(sed -n 's/^SIGN_WITH=//p' ~/.config/skatespots/zsp.env)"; export SIGN_WITH`. `SIGN_WITH="$(sed -n 's/^SIGN_WITH=//p' ~/.config/skatespots/zsp.env)"; export SIGN_WITH`.
Complete non-interactive publish: Complete non-interactive publish:
`SIGN_WITH="$(sed -n 's/^SIGN_WITH=//p' ~/.config/skatespots/zsp.env)"; export SIGN_WITH; zsp publish --quiet zapstore.yaml` `SIGN_WITH="$(sed -n 's/^SIGN_WITH=//p' ~/.config/skatespots/zsp.env)"; export SIGN_WITH; zsp publish --quiet zapstore.yaml`
✅ **Published 1.6.1, 1.6.2 and 1.6.3 on 2026-10-12** — the app's usual path is an **inline ✅ **Published 1.6.1–1.6.4 on 2026-10-12/13** — the app's usual path is an **inline
`SIGN_WITH=<nsec1…>`** (the value lives only in the shell/history, never in `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` → the repo); verify the signer is the app identity first (`nak key public` →
`npub1yrnuj…` / hex `20e7c953…`). Use **`~/go/bin/zsp`** (v0.4.11) — the `npub1yrnuj…` / hex `20e7c953…`). Use **`~/go/bin/zsp`** (v0.4.11) — the

4
package-lock.json generated
View file

@ -1,12 +1,12 @@
{ {
"name": "skate-spots", "name": "skate-spots",
"version": "1.6.3", "version": "1.6.4",
"lockfileVersion": 3, "lockfileVersion": 3,
"requires": true, "requires": true,
"packages": { "packages": {
"": { "": {
"name": "skate-spots", "name": "skate-spots",
"version": "1.6.3", "version": "1.6.4",
"license": "AGPL-3.0-only", "license": "AGPL-3.0-only",
"dependencies": { "dependencies": {
"@bitcoinerlab/secp256k1": "^1.2.0", "@bitcoinerlab/secp256k1": "^1.2.0",

View file

@ -1,7 +1,7 @@
{ {
"name": "skate-spots", "name": "skate-spots",
"private": true, "private": true,
"version": "1.6.3", "version": "1.6.4",
"license": "AGPL-3.0-only", "license": "AGPL-3.0-only",
"type": "module", "type": "module",
"homepage": "https://skate-spots.org", "homepage": "https://skate-spots.org",

View file

@ -1,3 +1,11 @@
🩹 Crew chat sends with Amber
- Sending to a crew no longer fails with "Amber didn't respond". The approvals
now come one at a time instead of all at once, so each one lands. (A 2-person
crew still needs a few approvals — that's the encrypted-message cost.) For
fewer taps, the crew's Private chat needs about one approval per message.
---
🧹 Fewer signer pop-ups 🧹 Fewer signer pop-ups
- Navigating around no longer re-decrypts your messages over and over, so the - Navigating around no longer re-decrypts your messages over and over, so the
Amber app stops flashing as you move between screens. New messages are pulled Amber app stops flashing as you move between screens. New messages are pulled