fix: Fix version bump verification

[Cal-L]

Description

This relaxes the version bump script to verify both iOS and Android bumps upwards

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.

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.

---

Note

Low Risk
Low risk shell-script change limited to build version validation; main impact is potentially blocking releases if either platform’s build number doesn’t strictly increase.

Overview
Updates scripts/set-build-version.sh to stop requiring Android and iOS build numbers to be in sync, and instead validates the provided VERSION_NUMBER is greater than each platform’s current value.

Improves logging by printing CURRENT_ANDROID_VERSION_NUMBER and CURRENT_IOS_VERSION_NUMBER, and routes version-regression failures through log_and_exit for consistent error handling.

^{Reviewed by Cursor Bugbot for commit 7f04caa. Bugbot is set up for automated code reviews on this repo. 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: 97%

click to see 🤖 AI reasoning details

E2E Test Selection:
The change is limited to scripts/set-build-version.sh, a build utility script used during the release/versioning process. The modification:

1. Removes the strict requirement that Android and iOS version numbers must be in sync before proceeding (previously blocked if they differed).
2. Replaces the single combined version check with two independent checks — one for Android and one for iOS — each using log_and_exit for consistent error handling.
3. Improves logging to show platform-specific current version numbers.

This change has zero impact on:

• App source code or runtime behavior
• E2E test infrastructure or test files
• Any controllers, components, or user flows
• Navigation, confirmations, accounts, networks, or any other testable feature area

No E2E tests need to run for this change. It is purely a build tooling improvement that allows Android and iOS build numbers to diverge (useful when platforms are versioned independently) while still ensuring the new version number is strictly greater than the current one on each platform.

Performance Test Selection:
This is a build script change with no impact on app runtime performance, UI rendering, data loading, or any measurable performance characteristic. No performance tests are needed.

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