docs: describe Android .apk support in the CLI and GitHub Action - #19
Merged
Merged
Conversation
crkingston
approved these changes
Sep 29, 2026
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.
The CLI and build-push Action already accept Android APKs, but their descriptions still imply iOS-only support or limited beta availability. Update the Action metadata, CLI file argument help, and README to describe iOS artifacts and standalone Android
.apkuploads.The README also identifies unsupported app bundles, XAPK/APK-set containers, and split APKs, and adds an Android GitHub Action example. No behavior changes.
Validation:
go test ./...passed with the repository's pinned Go 1.26.0 toolchain;git diff --checkpassed. No tests assert the old help text. There is no mise or Makefile test task.