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