From bf378f668e965acf8b8aa9c5df6bbec320caa317 Mon Sep 17 00:00:00 2001 From: Ross Golder Date: Tue, 6 Oct 2026 09:20:28 +0700 Subject: [PATCH] Release 2.1.3 Documentation only. No application code changed since 2.1.2, so the APK is functionally identical and only versionCode and versionName differ. Published to repair the ZapStore listing, whose Install button was greyed out. The relay had rejected the kind 3063 asset event that carries the APK, because it requires a version_code tag on any asset with an android- platform and the publish action was not emitting one. The release event survived and pointed at an asset event the relay did not have, which left a listing with no APK behind the button. The rejection was invisible because the action awaited an array of promises rather than the promises themselves, so the run exited 0 having logged "published kind 3063". Both defects are fixed in zapstore-publish v1.0.2, which release.yml picks up through @v1. This also carries the listing icon from #87 into a published event, which had never happened before: zapstore.yaml had no icon field, and that fix landed after 2.1.2 was tagged. Verified against the built artifact rather than the source file, which is the check that catches a typo the version grep cannot: package: name='org.golder.sms2webhook' versionCode='7' versionName='2.1.3' platformBuildVersionName='16' ./gradlew check passes. The on-device smoke test in step 4 of the checklist is skipped: nothing touching the sync, uploads, permissions or WorkManager changed, so the only new input is the published listing. --- CHANGELOG.md | 23 +++++++++++++++++++++++ sms2webhook/build.gradle | 4 ++-- 2 files changed, 25 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index ce59061..4b69859 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,28 @@ # Changelog +## [2.1.3] - 2026-10-06 + +Documentation only. **No application code changed since 2.1.2**, so the APK is +functionally identical; only `versionCode` and `versionName` differ. + +Published to repair the ZapStore listing. The **Install button was greyed out** +because the relay had rejected the asset event that carries the APK, so there was +nothing for the button to install. + +The relay requires a `version_code` tag on any asset event with an `android-` +platform, and the publish action was not emitting one. The run still reported +success, because the action awaited an array of promises rather than the promises +themselves, so the relay's rejection surfaced as noise instead of an error. Both +are fixed in zapstore-publish v1.0.2; this release exists to publish an asset +event the relay accepts. + +### 📚 Documentation +- **The ZapStore listing now carries the app icon.** `zapstore.yaml` gained an + `icon:` field, so the listing no longer shows a placeholder letter in place of + the app icon. +- **The release checklist names the icon's upload line.** A publish that silently + skipped the icon would otherwise look successful. + ## [2.1.2] - 2026-10-06 Documentation only. **No application code changed since 2.1.1**, so the APK is diff --git a/sms2webhook/build.gradle b/sms2webhook/build.gradle index dfc5930..3290764 100644 --- a/sms2webhook/build.gradle +++ b/sms2webhook/build.gradle @@ -53,8 +53,8 @@ android { applicationId "org.golder.sms2webhook" minSdk 28 targetSdk 36 - versionCode 6 - versionName "2.1.2" + versionCode 7 + versionName "2.1.3" testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"