From d4d31ec35bda004082dc6cc56c77d6fb0a67381d Mon Sep 17 00:00:00 2001 From: Ross Golder Date: Tue, 6 Oct 2026 12:20:34 +0700 Subject: [PATCH] Record the Zapstore listing repair in the 2.2.0 entry PR #89 proposed a 2.1.3 release to repair the Zapstore listing, whose Install button was greyed out. It cannot ship as written: #88 has since merged and master already declares versionCode 7 / 2.2.0, so rebasing #89 would move versionName backwards and label the main-screen redesign as 2.1.3. The repair is a new publish, not a version rollback. release.yml pins rossigee/zapstore-publish@v1, so tagging 2.2.0 picks up the fixed v1.0.2 and re-emits the asset event with a version_code tag the relay accepts. Carries across the useful half of #89's entry: the listing repair, and the note that this is the first release where the icon from #87 reaches a published event. Drops its "documentation only" framing, which was true of 2.1.3 and is not of 2.2.0. Also brings the entry up to date for #90's documentation work and the 146 tests that now exist. --- CHANGELOG.md | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 11310d9..b72c6de 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,14 @@ Minor: the main screen is redesigned, and the app now uploads only what you received. No longer sending your sent messages is a deliberate behaviour change. +Also the release that repairs the ZapStore listing, whose **Install button was +greyed out**. The relay had rejected the asset event carrying the APK because it +requires a `version_code` tag that the publish action was not emitting, while the +release event survived and pointed at an asset the relay did not have. The run still +reported success, because the action awaited an array of promises rather than the +promises themselves, so the rejection surfaced as noise rather than an error. Both +are fixed in zapstore-publish v1.0.2, which `release.yml` picks up through `@v1`. + ### ๐ŸŽจ Main screen - **One status line instead of three counters.** The screen showed Inbox / Uploaded / Failed plus a progress bar, which answered "what has happened in my history" @@ -37,10 +45,17 @@ received. No longer sending your sent messages is a deliberate behaviour change. count derived from it, and it made inbox-minus-uploaded drift positive by roughly the size of your sent history. **Existing installs will show fewer messages immediately.** +### ๐Ÿ“š Documentation +- **The ZapStore listing now carries the app icon.** `zapstore.yaml` gained an + `icon:` field; without it the store showed a placeholder letter. This is the first + release where it reaches a published event. +- The webhook contract is documented for the first time: which status codes mean + delivered, retried, or permanently discarded, and the setup QR payload format. + ### ๐Ÿงช Tests -- 143 unit tests, up from 129. Added `SyncStatusTest` and `CacheDiagnosticsTest`, - covering the status mapping and the report-once rule. `StatisticsTest` was removed - with the counters it tested. +- 146 unit tests, up from 129. Added `SyncStatusTest`, `CacheDiagnosticsTest`, and + coverage for reporting an unreadable inbox rather than claiming zero outstanding. + `StatisticsTest` was removed with the counters it tested. ---