Add lightweight mt-check-release-needed workflow to trigger release on stale tag or data changes

[Copilot]

This introduces a new fast workflow in shared-overwrite/.github/workflows that runs on manual dispatch and pushes to master, and decides whether mt-release.yml should be triggered. It mirrors the release-needed intent from existing scripts while avoiding submodule-heavy setup.

• New workflow: release-needed gate

  • Added mt-check-release-needed.yml with:
    • on.workflow_dispatch
    • on.push.branches: [master]
    • concurrency guard per workflow/ref.

• Release decision logic

  • Checks last release tag timestamp and marks release needed if older than 7 weeks (4233600 seconds).
  • If no release tag exists, immediately triggers mt-release.yml.

• Data change detection since last release tag

  • Compares LAST_TAG..HEAD and exits on first match across:
    • app-android/src/main/res/values/gtfs_rts_values_gen.xml
    • app-android/src/main/res/raw/**
    • app-android/src/main/res-current/values/current_gtfs_rts_values_gen.xml
    • app-android/src/main/res-current/raw/**
    • app-android/src/main/res-next/values/next_gtfs_rts_values_gen.xml
    • app-android/src/main/res-next/raw/**

• Trigger behavior

  • Runs gh workflow run mt-release.yml when either condition is true:
    • release too old, or
    • tracked data changed.
  • Uses GH_TOKEN from secrets.MT_PAT.
  • Adds explicit error handling and actionable failure messaging for dispatch failures.

if [[ "${RELEASE_TOO_OLD}" == "true" || "${DATA_CHANGED}" == "true" ]]; then
  gh workflow run mt-release.yml
fi

[gemini-code-assist]

Code Review

This pull request introduces a new GitHub Actions workflow, mt-check-release-needed.yml, which automates the decision to trigger a release based on a seven-week time limit or detected changes in specific Android resource directories. The review feedback recommends enhancing the tag detection logic to ensure the identified tag is reachable from the current branch and suggests optimizing the file change detection by replacing the loop with a single git diff call for improved efficiency and clearer logging.

[mmathieum]

TODO:

• what if we want to update data with mt-sync-code-data.yml but not release it?
  • use #skipci in git commit message?
• we can't keep both this new script and the current mt-sync-code-data.yml steps that trigger mt-release.yml themselves