chore(runway): cherry-pick chore(ci): derive RC slack notification changelog from git ancestry

[runway-github]

• chore(ci): derive RC slack notification changelog from git ancestry (chore(ci): derive RC slack notification changelog from git ancestry #28676)

Description

RC Slack notifications previously parsed CHANGELOG.md with
@metamask/auto-changelog. It wasn't working because the release
changelog is on a different branch and do not follow the format we want
for the slack notification. This change builds the “What’s in this RC”
section from git instead:

• A = git merge-base HEAD <base> (default origin/main,
  overridable via CHANGELOG_MERGE_BASE_REF)
• B = HEAD
• List commits with git log --ancestry-path A..B so only commits
  on the path between the fork point and the RC tip are included.

The reusable Slack workflow checkout is updated from fetch-depth: 1 to fetch-depth: 0 so merge-base has enough history on
the runner.

Changelog

CHANGELOG entry: null

Related issues

Fixes:
https://consensyssoftware.atlassian.net/browse/INFRA-3482
https://consensyssoftware.atlassian.net/browse/MCWP-442

Manual testing steps

Feature: RC Slack notification changelog

  Scenario: Verify git-based commit list on a release branch
    Given a clone with full history and a remote tracking branch (e.g. origin/main)
    When CHANGELOG_MERGE_BASE_REF is unset or set to origin/main and the script runs with SLACK_BOT_TOKEN and TEST_CHANNEL
    Then the Slack message lists commits from git log --ancestry-path $(git merge-base HEAD origin/main)..HEAD and respects the entry cap

  Scenario: GitHub Actions reusable workflow
    Given the slack-rc-notification workflow runs after an RC build
    When the checkout uses fetch-depth 0
    Then merge-base and ancestry-path succeed and the notification posts without shallow-clone errors

Screenshots/Recordings

Before

After

Message preview
link

--- 96ee8a5

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

click to see 🤖 AI reasoning details

E2E Test Selection:
The two changed files are purely CI/notification infrastructure:

1. .github/workflows/slack-rc-notification.yml: A single-line change from fetch-depth: 1 to fetch-depth: 0 to enable full git history fetching. This is required by the new git-based commit listing logic in the script.

2. scripts/slack-rc-notification.mjs: A significant refactor of the Slack RC notification script that replaces CHANGELOG.md parsing with git history-based commit listing (git merge-base + git log --ancestry-path). Also adds dry-run mode and removes TEST_CHANNEL override.

Neither file touches any app source code, React Native components, controllers, navigation, state management, or any code path exercised by E2E or performance tests. These changes only affect the post-RC-build Slack notification mechanism. No E2E tests or performance tests are warranted.

Performance Test Selection:
The changes are limited to a CI notification workflow and its associated script. No app code, rendering, state management, or performance-sensitive paths are affected. Performance tests are not 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