Description

This PR updates the post-#29305 CI requirement filters so locale translation JSON changes are treated as E2E-ignorable.

Locale-only PRs under locales/languages/**/*.json should now skip Smart E2E selection plus Android/iOS E2E builds and smoke tests. The change also adds the same locale rule to the Android/iOS platform-or-ignorable filters, so mixed platform + locale changes keep platform-specific E2E behavior instead of expanding to both platforms.

Changelog

CHANGELOG entry: null

Related issues

Fixes: MCWP-440

Manual testing steps

Feature: CI requirements for locale translation changes

  Scenario: locale translation PR skips E2E
    Given a pull request changes only files under locales/languages/**/*.json
    When the ci workflow runs get-requirements
    Then Smart E2E selection is skipped
    And Android E2E build and smoke test jobs are skipped
    And iOS E2E build and smoke test jobs are skipped
    And pr-not-ready-for-e2e does not block merge for the ignorable-only change

Screenshots/Recordings

Before

N/A

After

N/A

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.