forked from upstream-mirrors/quik
Use persistent release signing key and verify APK certificates in CI
Build and Release APK / Build APK (push) Successful in 8m18s
Build and Release APK / Build APK (push) Successful in 8m18s
This commit is contained in:
@@ -33,6 +33,35 @@ The reset removes local Matrix accounts, room mappings, encryption stores and br
|
||||
SMS messages, Quik settings, the Manager ID and the backfill limit are preserved.
|
||||
New rooms use contact names from Android, and SMS history is copied again up to the configured limit.
|
||||
|
||||
## Persistent release signing
|
||||
|
||||
Release APKs require the permanent signing key. Missing signing configuration fails the build;
|
||||
release builds never fall back to a generated debug key. Pull requests build and test Debug
|
||||
without release secrets and do not publish releases.
|
||||
|
||||
Gitea repository **Settings → Actions → Secrets** must contain:
|
||||
|
||||
- `ANDROID_KEYSTORE_BASE64`: base64-encoded permanent PKCS12 keystore.
|
||||
- `ANDROID_KEYSTORE_PASSWORD`: keystore password.
|
||||
- `ANDROID_KEY_ALIAS`: signing key alias.
|
||||
- `ANDROID_KEY_PASSWORD`: private key password.
|
||||
|
||||
The public certificate and its SHA-256 fingerprint are tracked in `.gitea/release-signing.crt`
|
||||
and `.gitea/release-signing.sha256`. CI checks the restored key and the finished Release APK
|
||||
against this fingerprint before publishing. The temporary CI key is removed even after failure.
|
||||
Do not regenerate the signing key between builds; back up the key and passwords securely.
|
||||
The initial local backup is `.secrets/quik-release.p12` with credentials in
|
||||
`.secrets/release-signing.json`. These private files are ignored by Git and must not be committed.
|
||||
|
||||
For a local Release build, set `ANDROID_KEYSTORE_PATH`, `ANDROID_KEYSTORE_PASSWORD`,
|
||||
`ANDROID_KEY_ALIAS` and `ANDROID_KEY_PASSWORD`. Existing local `.gradle/.gradlerc` properties
|
||||
and the legacy CI environment names are also supported. Debug APKs use a separate application ID
|
||||
and are intended for development.
|
||||
|
||||
The former builds 50 and 51 used different disposable debug certificates. The new permanent key
|
||||
cannot update either installation in place; migrating once to the new certificate requires a
|
||||
reinstall. Subsequent Release updates keep the same signature.
|
||||
|
||||
## Building and Releasing (Fork CI/CD)
|
||||
|
||||
The project uses Gitea Actions for CI/CD:
|
||||
|
||||
Reference in New Issue
Block a user