ci: use a Trafero-specific persistent CI keystore path
dev / Build debug APK (push) Successful in 15s
release / Build & attach release APK (push) Successful in 25s

The runner cache already held a release.jks minted by another project with a different store password, so packageRelease failed with "keystore password was incorrect". Mint and reuse trafero-release.jks instead.
This commit is contained in:
nick committed 2026-09-21 18:02:14 +12:00
1 parent ef12660b6a
commit b8ac68b363
2 files changed
+16 -12

No files matched your search

+5 -3
View File
@@ -25,9 +25,11 @@ before publishing anywhere real.
## CI (Gitea Actions)
`release.yml` mints one persistent keystore on the runner at
`/var/lib/gitea-runner/work/release.jks` (same parameters as above) and
copies it to `keystore/release.jks` for every build, so all CI release
APKs share one signing key and users can upgrade in place.
`/var/lib/gitea-runner/work/trafero-release.jks` (same parameters as
above, except `CN=Trafero CI`) and copies it to `keystore/release.jks`
for every build, so all CI release APKs share one signing key and users
can upgrade in place. The file is project-specific (`trafero-` prefix)
because the runner cache directory is shared between repositories.
**Important:** locally-built (and debug) APKs have a *different*
signature from CI release APKs — installing a CI release build over a