chore: increase js bundle to 53

[tommasini]

Description

Increase JS bundle 1 MB

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.

---

Note

Low Risk
Low risk: workflow-only change that just relaxes the CI bundle-size gate by 1 unit and doesn’t affect runtime code.

Overview
CI bundle-size gating has been relaxed slightly. The js-bundle-size-check step in .github/workflows/ci.yml now allows an iOS main.jsbundle size threshold of 53 instead of 52 when running ./scripts/js-bundle-stats.sh.

^{Written by Cursor Bugbot for commit 3c0f0a4. This will update automatically on new commits. Configure here.}

[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: 95%

click to see 🤖 AI reasoning details

E2E Test Selection:
The change is a simple CI configuration adjustment that increases the iOS JS bundle size limit from 52 MB to 53 MB in the CI workflow. This is purely an administrative/infrastructure change that:

1. Does not modify any application code
2. Does not change any test infrastructure or test files
3. Does not affect any user-facing functionality
4. Simply adjusts a threshold value to allow a slightly larger bundle to pass CI checks

This type of change has zero impact on application behavior and requires no E2E test validation. The bundle size check script (js-bundle-stats.sh) is a simple file size comparison utility that runs during CI to ensure the bundle doesn't exceed a specified limit. Increasing this limit from 52 to 53 MB is a routine maintenance task that doesn't warrant running any E2E tests.

Performance Test Selection:
This change only adjusts a bundle size threshold in CI configuration. It does not modify any application code, UI components, data loading logic, or any code paths that could impact app performance. No performance tests are needed for this administrative CI change.

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

[Gudahtt]

LGTM!

[metamaskbot]

Missing release label release-7.69.0 on PR. Adding release label release-7.69.0 on PR and removing other release labels(release-7.70.0), as PR was cherry-picked in branch 7.69.0.