Description

The Set secrets step in .github/workflows/build.yml required every GitHub secret to be explicitly listed in the workflow YAML (e.g. SEGMENT_WRITE_KEY: ${{ secrets.SEGMENT_WRITE_KEY }}). This meant that adding or renaming a secret in builds.yml also required running yarn build:workflow:update-secrets to regenerate that list — a manual, easy-to-forget maintenance step.
This PR eliminates that requirement by passing the entire secrets context as a single JSON blob via toJSON(secrets), which set-secrets-from-config.js then parses at runtime. The script already had all the logic to select and remap only the relevant secrets for the active build via CONFIG_SECRETS — it just needed the values delivered differently.
Changes:

• Replace the 44-line explicit secrets env: block in build.yml with ALL_SECRETS: ${{ toJSON(secrets) }}
  Update set-secrets-from-config.js to look up secret values from the parsed ALL_SECRETS object instead of individual env vars
• Delete scripts/generate-build-workflow-secrets-env.js (no longer needed)
  Remove the build:workflow:update-secrets yarn script from package.json

To test: chore/testing-branch

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.