Add GitHub Action to publish releases to Play Store Internal Test track

[Copilot]

Why is this important?

Automates Play Store deployments similar to existing Firebase App Distribution workflow. All Q42 apps use Play Store, so automating pushes to internal test track eliminates manual upload steps.

Notes

New workflow: .github/workflows/playstore-internal.yml

• Triggers on release/* branches and manual dispatch
• Builds signed AAB using existing keystore secrets
• Uploads to Play Store Internal Test track via r0adkll/upload-google-play@v1
• Sets inAppUpdatePriority: 2 and status: completed

Setup required:

• Add PLAYSTORE_SERVICE_ACCOUNT_JSON secret (service account with Play Developer API access)
• Update packageName: nl.q42.template to your app's package name

Security:

• Explicit permissions: contents: read to limit GITHUB_TOKEN scope
• CodeQL validated, no alerts

README updated with service account creation steps and Play Developer API documentation links.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Github Action to publish release to Playstore Internal Test track</issue_title>
<issue_description>We currently have a Github action to push releases to Firebase App Distribution.

Since 100% of our apps use play store obviously, it might be nice to automate andy pushes to a release branch to the internal test track of a connected Play Store app.

To implement this, I'd say it is fine to create a dummy app q42.template in hte play console and simply don't release it to production; just internal test track</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Github Action to publish release to Playstore Internal Test track #108

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.