chore: Proposal 2 yaml anchors

[tommasini]

Description

Changelog

CHANGELOG entry:

Related issues

Fixes:

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.

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)
• Risk Level: low
• AI Confidence: 92%

click to see 🤖 AI reasoning details

This PR introduces a new build environment configuration system using YAML files with anchors. The changes consist entirely of:

1. New CI/build infrastructure files:

   • A new GitHub Actions workflow (build.yml) for building the mobile app
   • New YAML configuration files for different environments (prod, rc, exp)
   • A shared YAML file with anchors for common configuration
   • A Node.js script to load and resolve YAML configurations
   • Documentation (README.md)

2. Dev dependency addition:

   • js-yaml package added to devDependencies in package.json

Why no E2E tests are needed:

• All changes are to build/CI infrastructure, not application code
• No modifications to any existing app code, components, or controllers
• The js-yaml package is a dev dependency only (not bundled in the app)
• No changes to E2E test infrastructure or test files
• The new workflow and configs are for building the app, not for runtime behavior
• No user-facing features are affected

While package.json is marked as critical, the only change is adding a dev dependency for build tooling, which doesn't affect the runtime application or require E2E validation.

View GitHub Actions results