chore: update github-tools to v1.1.3

[Qbandev]

Description

Updates github-tools to v1.1.3 in release workflows.

Changes

• Updated update-release-changelog.yml to use github-tools@v1.1.3

What's included in v1.1.3

• Fixed: Prevent changelog PR creation when branches are in sync (#177)

See github-tools v1.1.3 release notes.

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/INFRA-3167

Manual testing steps

Feature: Release changelog workflow

  Scenario: Workflow uses updated github-tools version
    Given the workflow configuration is updated

    When a release branch receives a push
    Then the workflow uses github-tools v1.1.3

Screenshots/Recordings

N/A - workflow configuration change only

Before

N/A

After

N/A

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.

[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)
• Risk Level: low
• AI Confidence: 95%

click to see 🤖 AI reasoning details

The change is a minor version bump (v1.1.2 → v1.1.3) of an external GitHub Action used in the release changelog workflow. This workflow only runs on pushes to release branches and handles automated changelog generation. It does not affect:

• Application source code
• E2E test infrastructure
• Any user-facing features or flows
• Core wallet functionality
• Controllers, Engine, or any critical paths

This is purely a CI/CD maintenance change with no functional impact on the mobile app itself. No E2E tests need to be run as there is no application code being modified that could affect user-facing behavior.

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