ci: test play store validation workflow

[joaoloureirop]

Description

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/MCRM-73
https://consensyssoftware.atlassian.net/browse/MCWP-478

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 97%

click to see 🤖 AI reasoning details

E2E Test Selection:
All 9 changed files are exclusively Android CI/build infrastructure changes with zero impact on app runtime behavior:

1. New GitHub Action (.github/actions/android-play-store-manifest-check/action.yml) for Play Store manifest validation - pure CI tooling
2. build.yml additions for Play Store lint/bundle validation steps - CI workflow only
3. slack-rc-notification.yml permissions + artifact download step - CI notification only
4. android/app/build.gradle: adds lint baseline reference - build config only, no runtime change
5. android/app/lint-baseline.xml: new lint baseline suppressing pre-existing issues - no runtime impact
6. android/gradle.properties: adds byte-buddy Jetifier ignorelist - build tooling fix, no runtime behavior change
7. android/gradle.properties.github: same byte-buddy fix for CI builds
8. scripts/android-play-store-check-slack.mjs: new non-blocking CI check script
9. scripts/slack-rc-notification.mjs: adds optional Play Store check report to Slack notifications

None of these changes touch app source code, React Native components, controllers, navigation, or any user-facing functionality. The changes are entirely confined to Android build tooling, CI workflows, and notification scripts. No E2E tests are needed to validate these changes.

Performance Test Selection:
All changes are CI/build infrastructure and Gradle configuration. No app source code, UI components, data loading, or runtime behavior is modified. Performance tests are not applicable.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud