[TECHNICAL] Workflow that builds an unsigned app with version and variant#4751
Merged
[TECHNICAL] Workflow that builds an unsigned app with version and variant#4751
Conversation
de6b276 to
0cc24e7
Compare
Collaborator
Author
will do, in order to keep consistency as well |
2e9dc0b to
fcf3aeb
Compare
jesmrec
added a commit
that referenced
this pull request
Jan 15, 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
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.
Reusable workflow to be called for any other workflow to get an apk artifact to be used in testing or any other purposes. Artifact is unsigned, since the keys and the keystore are responsibility on the calling workflow.
Inputs: build variant and commit/tag/branch
Related Issues
App:
ReleaseNotesViewModel.ktcreating a newReleaseNote()with String resources (if required)QA