v1.2.0

Added

• TB_CHECK_NAME: names the GitHub pull request check TestingBot / <name> (for example iOS, Android) so separate EAS jobs on one commit post separate checks (forwarded as --check-name, @testingbot/cli 1.4.0+). The Android and iOS examples set it.

Fixed

• TB_GH_REPO_NAME accepts owner/repo (the value of github.repository) and derives the owner, so the run's repository is registered correctly and the pull request check posts.

Docs

• README: job-level env, pull request expressions being null on manual triggers, and a link to https://testingbot.com/support/app-automate/maestro/ci-cd/expo-eas

v1.1.2

• TB_GH_REPO_NAME accepts ${{ github.repository }} (owner/repo) and derives the owner, so the GitHub status check is posted with a single variable. Previously the examples produced owner/owner/repo and no check.
• Examples and README: set env at job level; only pass TB_GH_PR_NUMBER in pull_request-triggered workflows (the expression is null otherwise and EAS rejects the job).

v1.1.1

Maintenance release: updates the development dependencies flagged by Dependabot (vitest 5, vite 8, esbuild; none are shipped in the package) and moves npm publishing to trusted publishing (OIDC with provenance), so no long-lived npm token is needed. No behaviour change.

v1.1.0

First npm release of @testingbot/eas-workflow: run Maestro flows on TestingBot from EAS Workflows.

- uses: eas/download_build
  id: download
  with:
    build_id: ${{ needs.build_android.outputs.build_id }}
- id: testingbot
  run: |
    npx --yes @testingbot/eas-workflow@v1 \
      --app-file ${{ steps.download.outputs.artifact_path }} \
      --flows ./.maestro

• Wraps @testingbot/cli 1.2.0 or newer and reads its JSON results document: console_url, app_id, run_urls, run_status, outcome, error, flow counts, flow name lists and a one-line summary as step outputs, ready for github-comment and slack jobs.
• Exit codes follow the CLI: 0 passed, 2 flows failed, 1 CLI or infrastructure error.
• --app-file, --app-url (EAS Build URLs, .tar.gz iOS simulator builds) or --app-binary-id; every other flag is forwarded to testingbot maestro.
• TB_GH_* variables record commit, branch, pull request and repository on the run, which also posts a TestingBot / tests status check when the TestingBot GitHub App is installed.
• Credentials from EAS project secrets (TB_KEY, TB_SECRET); the ${{ secrets.X }} syntax is not supported in EAS Workflows.

Docs: https://testingbot.com/support/app-automate/maestro/ci-cd#expo