austinried
e700c99796
docs: label the fingerprints as keytool/apksigner format
2026-10-08 18:52:44 +00:00
austinried
6af43c9c16
docs: drop the private Play Console references from signing/README
2026-10-08 18:52:44 +00:00
austinried
4f04129b0e
docs: show both fingerprint formats with tool labels
2026-10-08 18:52:44 +00:00
austinried
772ab5f563
docs: note the fingerprint formats and normalize the release-notes one
2026-10-08 18:52:44 +00:00
austinried
1eb7c136bf
docs: link F-Droid's signing keys and the nightly keystore
2026-10-08 18:52:44 +00:00
austinried
17ba581f88
docs: list F-Droid before nightly in the signing channels
2026-10-08 18:52:44 +00:00
austinried
76f2e4014c
docs: put the release certificate before the nightly section
2026-10-08 18:52:44 +00:00
austinried
3d2ec5e931
docs: unwrap the lines in signing/README.md
2026-10-08 18:52:44 +00:00
austinried
368f53d589
release: attach the signed AAB to the GitHub release
...
Publish the exact bundle sent to Play alongside the APK, cover both in
SHA256SUMS and the release notes, and document verifying the AAB.
2026-10-08 18:52:44 +00:00
austinried
3f3db71f14
docs: commit the release signing certificate and fingerprint
...
Add the release key's public certificate (signing/release-certificate.pem)
and its SHA-256 to signing/README.md.
2026-10-08 18:52:44 +00:00
austinried
e60b2d9910
rename the next build back to nightly
...
Rename the build type, workflow, artifact and app id (com.subtracks.nightly)
from next to nightly, and update the signing docs to match.
2026-10-08 18:52:44 +00:00
austinried
f6d1d548e4
docs: correct the signing notes for Play App Signing
...
Google re-signs Play-delivered apps, so the release key is only the
upload key there and signs the AAB we send; the installed app verifies
against Google's app signing certificate. The release key also signs the
GitHub-release APK.
2026-10-08 18:52:44 +00:00
austinried
d3373261d2
release: publish checksums and the signing certificate
...
Print the artifact SHA-256 and the APK signer certificate in the release
log, attach SHA256SUMS and the public release certificate to the GitHub
release, list the APK and certificate SHA-256 in the release notes, print
the next build checksums, and commit the next build's public certificate
with verification steps in signing/README.md.
2026-10-08 18:52:44 +00:00
austinried