Skip to content

chore: Bump github tools to 1.7.0#26804

Merged
Cal-L merged 1 commit into
mainfrom
chore/bump-github-tools-to-1.7.0
Mar 2, 2026
Merged

chore: Bump github tools to 1.7.0#26804
Cal-L merged 1 commit into
mainfrom
chore/bump-github-tools-to-1.7.0

Conversation

@Cal-L

@Cal-L Cal-L commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Description

This PR bumps the github tools version from v1 -> v1.7.0 (latest fixed release)

Changelog

CHANGELOG entry:

Related issues

Fixes: https://consensys.slack.com/archives/C02U025CVU4/p1772447777927309

Manual testing steps

CI should still be intact

Screenshots/Recordings

Before

After

Pre-merge author checklist

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

Medium Risk
CI-only change, but it updates the shared environment setup action used across Android/iOS builds and E2E runs, so failures would surface as broken pipelines rather than runtime issues.

Overview
Updates the GitHub Actions workflows for Android/iOS builds and E2E smoke/runs to use a pinned MetaMask/github-tools/.github/actions/setup-e2e-env@v1.7.0 instead of @v1.

This standardizes CI environment setup across build.yml, the dedicated E2E build workflows, and the E2E runner workflows, reducing drift from the moving v1 tag.

Written by Cursor Bugbot for commit c6a5096. This will update automatically on new commits. Configure here.

@Cal-L Cal-L requested a review from a team as a code owner March 2, 2026 17:09
@Cal-L Cal-L enabled auto-merge March 2, 2026 17:09
@github-actions

github-actions Bot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

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.

@metamaskbot metamaskbot added the team-mobile-platform Mobile Platform team label Mar 2, 2026
@github-actions

github-actions Bot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

🔍 Smart E2E Test Selection

  • Selected E2E tags: None (no tests recommended)
  • Selected Performance tags: None (no tests recommended)
  • Risk Level: low
  • AI Confidence: 85%
click to see 🤖 AI reasoning details

E2E Test Selection:
All 5 changed files are GitHub workflow files with identical changes: updating the MetaMask/github-tools/.github/actions/setup-e2e-env action from @v1 (floating tag) to @v1.7.0 (pinned version). This is a CI infrastructure version pinning change that:

  1. Does not modify any application code
  2. Does not change test logic or test files
  3. Is a best practice change for reproducibility (pinning to specific version)
  4. The @v1 floating tag likely already resolved to v1.7.0 or a compatible version

The affected workflows are:

  • build-android-e2e.yml (Android E2E builds)
  • build-ios-e2e.yml (iOS E2E builds)
  • build.yml (general builds with iOS setup)
  • run-e2e-smoke-tests-ios-flask.yml (Flask E2E tests)
  • run-e2e-workflow.yml (main E2E runner)

While these changes affect E2E infrastructure, they don't change the actual test execution logic or app behavior. The E2E tests themselves will run as part of the normal CI pipeline and will validate that the environment setup still works correctly. No specific test tags need to be selected because:

  1. No app functionality is changed
  2. The CI pipeline will naturally validate the workflow changes work
  3. This is a minor version pin, not a breaking change

Performance Test Selection:
No performance tests needed. These changes only affect GitHub workflow files for E2E environment setup (version pinning of an external action). No application code, UI components, data loading, or performance-critical paths are modified. The changes have zero impact on app runtime performance.

View GitHub Actions results

@Cal-L Cal-L added the needs-dev-review PR needs reviews from other engineers (in order to receive required approvals) label Mar 2, 2026
@github-project-automation github-project-automation Bot moved this to Needs dev review in PR review queue Mar 2, 2026
@Cal-L Cal-L added the No QA Needed Apply this label when your PR does not need any QA effort. label Mar 2, 2026
@github-project-automation github-project-automation Bot moved this from Needs dev review to Review finalised - Ready to be merged in PR review queue Mar 2, 2026
@Cal-L Cal-L added no-changelog no-changelog Indicates no external facing user changes, therefore no changelog documentation needed no changelog required No changelog entry is required for this change labels Mar 2, 2026
@Cal-L Cal-L added this pull request to the merge queue Mar 2, 2026
Merged via the queue into main with commit 7ccbf0e Mar 2, 2026
96 of 100 checks passed
@Cal-L Cal-L deleted the chore/bump-github-tools-to-1.7.0 branch March 2, 2026 21:35
@github-project-automation github-project-automation Bot moved this from Review finalised - Ready to be merged to Merged, Closed or Archived in PR review queue Mar 2, 2026
@github-actions github-actions Bot removed the needs-dev-review PR needs reviews from other engineers (in order to receive required approvals) label Mar 2, 2026
@github-actions github-actions Bot locked and limited conversation to collaborators Mar 2, 2026
@metamaskbot metamaskbot added the release-7.69.0 Issue or pull request that will be included in release 7.69.0 label Mar 2, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

no changelog required No changelog entry is required for this change No QA Needed Apply this label when your PR does not need any QA effort. no-changelog no-changelog Indicates no external facing user changes, therefore no changelog documentation needed release-7.69.0 Issue or pull request that will be included in release 7.69.0 size-XS team-mobile-platform Mobile Platform team

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants