You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# This flow is designed to be used to update the production track on the Play store. It does this by promoting the beta track build to production, triggered by the creation of a release tag.
1
+
# This flow is designed to be used to update the production and beta tracks on the Play store. It does this by promoting the beta track build to production, triggered by the creation of a release tag.
2
2
# As per the beta build, this does not actually do a build / upload, it simply promotes whatever's in beta to production. Best to create the
3
-
name: Android CI production release
3
+
name: Android Release
4
4
5
5
on:
6
6
push:
7
7
tags:
8
8
- v[0-9]+.[0-9]+.[0-9]+
9
+
- v[0-9]+.[0-9]+.[0-9]+-beta[0-9]+
9
10
10
11
jobs:
11
12
release:
12
13
name: Create GH release and promote Play store beta to release
upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
0 commit comments