Repository navigation
Publish to Google Play on every merge - #25
Merged
Merged
Conversation
The release workflow now also builds an App Bundle (-p:ForPlay=true makes the same build produce both the .apk and the .aab) and uploads it to the Play track named by the PLAY_TRACK repository variable, with the merged PR's title as "What's new". Until PLAY_TRACK is set the upload is skipped and the bundle is only kept as a workflow artifact. Adds a privacy policy page to the docs site, which Play requires for an app that reads contacts. Closes #24 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Closes #24
Every merge to master now goes to Google Play as well as to GitHub Releases. Both come from a single build, so they have the same version.
Changes
CallGuard.csproj:-p:ForPlay=truebuilds an App Bundle (.aab, the only format Play accepts) next to the.apk. Local builds are unchanged.release.yml:ForPlayand keeps the.aabin the workflow artifact next to the.apk.r0adkll/upload-google-play@v1, the same action GroceryList uses.PLAY_SERVICE_ACCOUNT_JSONPLAY_TRACK(internal/alpha= Closed testing /beta/production)PLAY_RELEASE_STATUS(completedby default, ordraft)PLAY_TRACKis set. Merging this PR changes nothing until the Play Console side is ready.docs/privacy.md: a privacy policy page, required by Play for apps that read contacts. It will be at https://asulwer.github.io/CallGuard/privacy.html and is linked from How it works.Checked locally
ForPlayRelease publish produces a signed.aaband.apk, both versionName 1.0.261113 and the same versionCode.🤖 Generated with Claude Code