Add new google-play-store-release job to GitHub Actions and update release documentation

Author: florentmaitre

.github/workflows/build.yml

@@ -179,4 +179,37 @@ jobs:
       - name: Publish release to GitHub
         run: ./gradlew publishToGitHub
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+  google-play-store-release:
+    runs-on: ubuntu-latest
+    if: github.event_name == 'push' && contains(github.ref, 'refs/tags/')
+    needs: build
+    environment:
+      name: google-play-store-release
+      url: https://play.google.com/store/apps
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          submodules: recursive
+
+      - name: Set up our JDK environment
+        uses: actions/setup-java@v4
+        with:
+          distribution: 'zulu'
+          java-version: '17'
+
+      - name: Publish release to Google Play Store
+        run: |
+          ./gradlew assembleProdRelease bundleProdRelease
+          curl -F 'file=@app/build/outputs/bundle/prodRelease/app-prod-release.aab' https://oma-portal.orange.fr/oma/api/v1/external/applications/${{ secrets.OMA_APP_ID }}/artifacts -H "apiKey:${{ secrets.OMA_APP_TOKEN }}"
+
+      - name: Store Google Play Store artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: google-play-store
+          path: |
+            app/build/outputs/apk/*/*/*.apk
+            app/build/outputs/bundle/*/*.aab

release/RELEASE.md

@@ -20,8 +20,10 @@ This file lists all the steps to follow when releasing a new version of OUDS And
   This task finds the next semantic version based on conventional commits and performs the following changes to the project:
 
     - Update `version` project property in `gradle.properties`.
+    - Update version of OUDS Android dependencies in various Markdown files.
     - Increment the app `versionCode` in associated `build.gradle.kts` file.
     - Update content of `CHANGELOG.md`.
+    - Archive the documentation in `docs/previousDocVersions/X.Y.Z`.
 
   You can optionally launch `prepareRelease` with a version property to force the release version:
 
@@ -31,7 +33,7 @@ This file lists all the steps to follow when releasing a new version of OUDS And
 
 - Verify the changes mentioned above, then commit and push.
 
-- Create a new pull request named `Prepare release X.Y.Z` on GitHub to merge your branch into `develop`.
+- Create a new pull request named `chore: prepare release X.Y.Z` on GitHub to merge your branch into `develop`.
 
 - Review and merge this pull request on GitHub.<br /><br />
 
@@ -102,3 +104,24 @@ This file lists all the steps to follow when releasing a new version of OUDS And
 - Verify the release notes using the preview tab.
 
 - Optionally check `Set as a pre-release` and click `Publish release`.<br /><br />
+
+### Publish release to Google Play Store
+
+- Go to [GitHub Actions](https://github.com/Orange-OpenSource/ods-android/actions), open the release workflow, click `Review deployments`, select
+  `google-play-store-release` and click `Approve and deploy`.
+
+- Go to [OMA Portal](https://oma-portal.orange.fr) and open the `Design System Toolbox [OUDS Demo]` dashboard.
+
+- Click `Integrations`, find the uploaded bundle in the `Artifacts` sections and click `Create release`.
+
+  ![Create OMA Portal release](images/google_play_store_release_01.png)
+
+- Progress through the various submission steps.
+
+- When step is `Store submissions`, select `Closed beta with Google Groups`, set `Email addresses` to `design-toolbox-android@googlegroups.com` and click
+  `Go for store submission`.
+
+  ![OMA Portal store submission](images/google_play_store_release_02.png)<br /><br />
+
+- To publish the release you have to click a last time on "Got to publication". You should receive a confirmation email from OMA with a "Published" status.
+-