chore: automates play store submission and upload to github releases#1927
Merged
Conversation
…. One for adding releases to our github page. One to submit our production releases to the play store through eas.
ErikSin
approved these changes
Jun 9, 2026
ErikSin
left a comment
Contributor
There was a problem hiding this comment.
Since the workflow_dispatch flow is for testing, i am approving so we can try it out.
But there is one comment that we should try and address first
Comment on lines
+32
to
+35
| version: | ||
| description: 'Release version short form (e.g. 10.5)' | ||
| required: true | ||
| type: string |
Contributor
There was a problem hiding this comment.
lets get rid of this input and extract the version from EAS directly!
After the Wait for EAS build to finish
we can write this action:
-name: Extract version from EAS build
id: eas_version
env:
BUILD_ID: ${{ steps.inputs.outputs.build_id }}
run: |
version=$(eas build:view "$BUILD_ID" --json | jq -r '.runtimeVersion')
echo "version=$version" >> $GITHUB_OUTPUT
And then anywhere you have steps.inputs.outputs.version replace with steps.eas_version.outputs.version. and you can get rid of line 152.
Your original code allows the developer to type in the wrong version that may not match with the version of the apk. So these additions avoid that.
ErikSin
pushed a commit
that referenced
this pull request
Jun 10, 2026
…1927) * Alters eas file for submit config. Adds two jobs to our build release. One for adding releases to our github page. One to submit our production releases to the play store through eas. * Some syntax corrections in workflow. * Removes input for version and gets it from EAS.
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 #1177
Summary
Testing
I need to merge this to develop to test it. The workflow has a manual trigger (workflow_dispatch) that lets me run just the GitHub Release job with a specific build ID and version — without triggering a real release or touching the Play Store. That is a much more complicated piece of code and doesn't hurt much if we have to test it out a few times, unlike the play store submission.
My plan once merged: run it manually with the v10.5 hotfix build. This gives us two things at once:
@ErikSin — Can you review this untested so I can merge this so I can run the test? The workflow_dispatch trigger only appears in the Actions tab once the workflow is on develop, unfortunately.