chore: update node-version-file in push-eas-update.yml

[weitingsun]

Description

We changed node-version-file from 20 to '.nvmrc' in setup-node-modules.yml (here) so we need to do the same in push-eas-update.yml.

testing workflow: https://github.com/MetaMask/metamask-mobile/actions/runs/22603948995

Changelog

CHANGELOG entry:null

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: CI-only change that just aligns Node setup with .nvmrc, though it could affect workflow runs if the file is missing or incompatible.

Overview
Updates the push-eas-update.yml GitHub Actions workflow to source the Node.js version from node-version-file: '.nvmrc' instead of hardcoding Node 20.

This is applied to both the fingerprint comparison job and the EAS update publish job, keeping CI Node version consistent with the repo’s configured version.

^{Written by Cursor Bugbot for commit 348449d. 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 modifies only the .github/workflows/push-eas-update.yml workflow file, replacing hardcoded node-version: '20' with node-version-file: '.nvmrc' in two places (fingerprint-comparison and push-update jobs). This is a CI infrastructure change that standardizes Node.js version sourcing to use the project's .nvmrc file instead of a hardcoded version. The change:

1. Does not modify any application code
2. Does not modify any E2E test infrastructure or test files
3. Only affects the OTA (Over-The-Air) update workflow, which is separate from E2E test execution
4. Is a simple configuration standardization for consistency

Since no application code or test infrastructure is affected, no E2E tests are required to validate this change.

Performance Test Selection:
This change only modifies CI workflow configuration for Node.js version sourcing. It has no impact on application code, UI rendering, data loading, or any runtime behavior that could affect app performance.

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

[Cal-L]

Lgtm