Repository navigation
Add tagged release flow with real APK signing - #3
Merged
Merged
Conversation
Pushing a vX.Y.Z tag now builds app:assembleRelease and publishes a GitHub Release with the minified APK attached and auto-generated notes, separate from the existing rolling debug-latest build. Since there's no managed release keystore yet, the release build type signs with the debug key so the APK stays installable. https://claude.ai/code/session_01J194Wop2SixMd1HPS5PbcS
Adds a release signingConfig that reads the keystore path and credentials from environment variables, falling back to debug signing when they're unset (e.g. local builds). The release workflow decodes a base64-encoded keystore secret and passes the credentials through so tagged releases are signed with a real release key instead of the debug key. https://claude.ai/code/session_01J194Wop2SixMd1HPS5PbcS
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
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/android-release.yml: pushing avX.Y.Ztag buildsapp:assembleReleaseand publishes a GitHub Release with the APK attached and auto-generated notes, separate from the existing rollingdebug-latestbuild.app/build.gradle.kts: thereleasebuild type now uses a real signing config (keystore path + credentials from environment variables), falling back to debug signing when those env vars aren't set (e.g. local builds).RELEASE_KEYSTORE_BASE64secret and passesRELEASE_KEYSTORE_PASSWORD,RELEASE_KEY_ALIAS,RELEASE_KEY_PASSWORDthrough to Gradle.Setup required before first tagged release
A release keystore has been generated and sent separately (not committed to the repo). To enable signed releases, add these repository secrets in GitHub (Settings → Secrets and variables → Actions):
RELEASE_KEYSTORE_BASE64RELEASE_KEYSTORE_PASSWORDRELEASE_KEY_ALIASRELEASE_KEY_PASSWORDIf these secrets are absent, the release workflow still runs and produces a debug-signed APK (with a CI warning), so the flow degrades gracefully.
Test plan
git tag v0.1.0 && git push origin v0.1.0Releaseworkflow runs, buildsassembleRelease, and publishes a GitHub Release with the APK attachedhttps://claude.ai/code/session_01J194Wop2SixMd1HPS5PbcS
Generated by Claude Code