Add SHA-256 certificate fingerprint to GitHub Releases - #89
Merged
Merged
Conversation
The release workflow now extracts the signing certificate's SHA-256 fingerprint from the built APK via keytool and includes it in the release notes, so it's easy to verify the APK signature and to copy the value when it's needed elsewhere (e.g. registering the app with Google Play Console). Also documents how to retrieve the fingerprint locally from the keystore or an APK. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018xRix1BfBRuXMh9P1rrj64
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.github/workflows/release.yml) now extracts the signing certificate's SHA-256 fingerprint from the built, signed APK viakeytool -printcertand publishes it in the GitHub Release notes under a new "Verify the APK signature" section.docs/DEPLOYMENT.md.Why
Having the SHA-256 certificate fingerprint on the release makes it easy to verify the APK's authenticity/signature before installing, and to copy the value when it's needed elsewhere — e.g. Google Play Console's app registration flow, which asks for the SHA-256 fingerprint of the app's signing certificate.
Test plan
python3 -c "import yaml; yaml.safe_load(open('.github/workflows/release.yml'))")main, confirm the "Get certificate fingerprint" step succeeds and the fingerprint appears correctly formatted in the published GitHub Release notes🤖 Generated with Claude Code
https://claude.ai/code/session_018xRix1BfBRuXMh9P1rrj64
Generated by Claude Code