fix(fdroid): correct AllowedAPKSigningKeys to the canonical CI release key

Published FOSS releases (v1.0.2, v1.0.3, v1.0.4) are signed by GitHub
Actions using secrets.RELEASE_KEYSTORE, whose certificate SHA-256 is
7cc8d2d568eb3d20a5e190e77baa97b3bde80782dd2576f29088a16c4ce47850
(verified via `apksigner verify --print-certs` on the published
rouse-context-1.0.4-foss.apk). The recipe previously declared the local
.signing/release.keystore cert (5394b7c7...), which does NOT match any
published release and would cause F-Droid's AllowedAPKSigningKeys check
to reject the upstream-signed asset.

Update the YAML value, the MaintainerNotes describing it, and the
matching docs/distribution.md reference so none of them tie the value to
the local keystore. Owner confirmed the CI key is canonical.

Part of #465.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Jason Monk 2026-06-28 10:25:07 -04:00
parent 9e71b65921
commit e36e8b4292
2 changed files with 11 additions and 4 deletions

View file

@ -73,10 +73,13 @@ Consequences for users:
(which loses app data). Pick one distribution per device and stay on it.
The release signing certificate SHA-256 (public, used as
`AllowedAPKSigningKeys`) is:
`AllowedAPKSigningKeys`) is the certificate that CI signs published releases
with (GitHub Actions `secrets.RELEASE_KEYSTORE`, not the local
`.signing/release.keystore`). Confirmed against the published v1.0.4 FOSS APK
via `apksigner verify --print-certs`:
```
5394b7c725925737dae18a320609efb0f69f8d028b0a1204157e1962dfe51dca
7cc8d2d568eb3d20a5e190e77baa97b3bde80782dd2576f29088a16c4ce47850
```
## F-Droid submission status

View file

@ -72,7 +72,7 @@ Repo: https://github.com/Monkopedia/rouse-context.git
# name is `rouse-context-<versionName>-foss.apk` (see release.yml). The tag /
# asset do not exist until the owner cuts the release — this is a template.
Binaries: https://github.com/Monkopedia/rouse-context/releases/download/v%v/rouse-context-%v-foss.apk
AllowedAPKSigningKeys: 5394b7c725925737dae18a320609efb0f69f8d028b0a1204157e1962dfe51dca
AllowedAPKSigningKeys: 7cc8d2d568eb3d20a5e190e77baa97b3bde80782dd2576f29088a16c4ce47850
Builds:
- versionName: 1.0.4
@ -141,7 +141,11 @@ MaintainerNotes: |-
* The FOSS release build matches the published GitHub Release APK
byte-for-byte apart from the v2/v3 APK Signing Block PSS salt, which
apksigcopier normalizes. F-Droid ships the upstream signature.
* AllowedAPKSigningKeys is the release signing cert SHA-256.
* AllowedAPKSigningKeys is the SHA-256 of the certificate that CI signs
published releases with (GitHub Actions `secrets.RELEASE_KEYSTORE`, NOT
the local `.signing/release.keystore`). Confirmed against the published
v1.0.4 FOSS APK (`rouse-context-1.0.4-foss.apk`) via
`apksigner verify --print-certs`.
* With no signing credentials present, AGP builds the release UNSIGNED
(the release signingConfig is left off the buildType); F-Droid verifies
reproducibility against the published signed asset and ships our