fix(build): v0.3.6.3 — fail-fast on missing keystore
release / Build & attach release APK (push) Successful in 2m21s

- signingConfigs.release now throws GradleException at config time
    when keystore/release.jks is missing, printing the exact keytool
    command from keystore/README.md instead of letting packageRelease
    die later with the cryptic
    "SigningConfig release is missing required property storeFile".

  - .gitea/workflows/release.yml now mints the dev keystore on the
    runner before assembleRelease (previously the signing config
    was empty on a fresh runner, so the release APK was never
    produced).

  - versionCode 29 → 30, versionName "0.3.6.2" → "0.3.6.3";
    APP_VERSION in SettingsViewModel bumped in lockstep; README
    "Current release" + intro paragraph + Changelog row updated.

  Refs: Incido Development Plan §11.
This commit is contained in:
Incido Developer committed 2026-08-20 05:28:00 +12:00
1 parent ef5a45201e
commit b95d1814f9
4 files changed
+63 -19

No files matched your search

+18
View File
@@ -49,6 +49,24 @@ jobs:
echo "ANDROID_SDK_ROOT=$SDK" >> $GITHUB_ENV
echo "PATH=$SDK/cmdline-tools/latest/bin:$SDK/platform-tools:$PATH" >> $GITHUB_ENV
# The release signing config in app/build.gradle.kts only attaches a
# storeFile when keystore/release.jks exists, and that .jks is
# gitignored -- so the CI runner must mint its own. We use the exact
# dev keystore documented in keystore/README.md (alias "incido",
# both passwords "incido_dev_keystore"). Move to a Gitea Actions
# secret + production keystore before publishing to Play / F-Droid.
- name: Generate dev release keystore
run: |
cd repo
mkdir -p keystore
keytool -genkey -noprompt -v \
-keystore keystore/release.jks \
-keyalg RSA -keysize 2048 -validity 10000 \
-alias incido \
-storepass incido_dev_keystore \
-keypass incido_dev_keystore \
-dname "CN=Incido Dev, OU=Local, O=Incido, L=Local, ST=Local, C=NZ"
- name: Build release APK
env:
GITHUB_TOKEN: ${{ secrets.TOKEN }}