Signed release APK and Google Play internal track upload - #108
Merged
Conversation
diegurrio
force-pushed
the
feature/android-play-upload
branch
2 times, most recently
from
August 16, 2026 03:51
6353a40 to
baee142
Compare
Contributor
|
@diegurrio please use stacked PRs it's a new GitHub feature and it's enabled in this repo. |
Collaborator
Author
You got it. |
diegurrio
changed the base branch from
main
to
feature/android-release-signing
August 16, 2026 12:32
diegurrio
force-pushed
the
feature/android-play-upload
branch
from
August 16, 2026 12:46
baee142 to
571f4a4
Compare
diegurrio
force-pushed
the
feature/android-play-upload
branch
from
August 16, 2026 14:57
571f4a4 to
6e16cfa
Compare
The release workflow's android job now signs the APK with the upload keystore secrets, builds the AAB, verifies both, publishes hawkeye-<version>-android.apk to the GitHub release, and uploads the AAB to the Google Play internal test track through a service account. Every Play-facing step is guarded on its secret, so forks keep producing the unsigned artifact and skip Play. Docs updated for the signed asset name, the new version code derivation, the Play testing channel, and the one time uninstall for users of self-signed pre-signing builds.
diegurrio
force-pushed
the
feature/android-play-upload
branch
from
August 16, 2026 14:58
6e16cfa to
1be6a96
Compare
diegurrio
marked this pull request as ready for review
August 16, 2026 18:05
17 tasks
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.
Second half of #106, stacked on #107 (needs to be merged first; its base is that branch, so this diff shows only its own changes).
Changes to
release.yml:android-apkjob becomesandroidand now decodes the upload keystore fromANDROID_UPLOAD_KEYSTORE_BASE64, buildsassembleRelease bundleRelease, and verifies both artifacts.hawkeye-<version>-android.apk, verified with--signed. A fork without secrets still builds and publisheshawkeye-<version>-android-unsigned.apk, today's exact behavior.r0adkll/upload-google-play, pinned to the v1.1.5 commit. It runs only whenPLAY_SERVICE_ACCOUNT_JSONis present, so the workflow is safe to merge before the Play Console setup finishes. Prerelease tags upload too; rc builds are what the internal track is for. The AAB is not attached to the GitHub release.Docs updated to match:
releasing.md(asset name, new version code table, Play section, removal of the stale rc warning),installation.md(APK installs as downloaded, Play testing channel),troubleshooting.md(downgrade and certificate mismatch causes, including the one time uninstall for self-signed builds from v0.3.0 and earlier),README.md,android/README.md(release signing section, version code formula, CI table), and the setup action description.Part of #106; the issue stays open until the manual console steps are done and a release tag has been validated end to end.