Skip to content

chore: automates play store submission and upload to github releases#1927

Merged
cimigree merged 3 commits into
developfrom
chore/automate-submission
Jun 9, 2026
Merged

chore: automates play store submission and upload to github releases#1927
cimigree merged 3 commits into
developfrom
chore/automate-submission

Conversation

@cimigree

@cimigree cimigree commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

closes #1177

Summary

  • Updates eas.json with submit config for Google Play
  • Adds two new jobs to the Build Release workflow:
    1. GitHub Release — automatically creates a GitHub Release with the APK (downloaded from R2) and release notes attached if they exist, every time a release PR is merged
    2. Play Store submission — automatically submits the production AAB to the Play Store via eas submit after every release build

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:

  1. Confirms the workflow actually works
  2. Gets v10.5 onto our GitHub releases page

@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.

cimigree added 2 commits June 4, 2026 14:36
…. One for adding releases to our github page. One to submit our production releases to the play store through eas.
@cimigree cimigree requested review from ErikSin and Copilot and removed request for Copilot June 4, 2026 19:33

@ErikSin ErikSin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 thread .github/workflows/build-release.yml Outdated
Comment on lines +32 to +35
version:
description: 'Release version short form (e.g. 10.5)'
required: true
type: string

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cimigree cimigree merged commit f47663c into develop Jun 9, 2026
10 checks passed
@cimigree cimigree deleted the chore/automate-submission branch June 9, 2026 21:56
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update Github Actions/EAS actions to automate Publishing of App

2 participants