sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

build-tools adds eas/deploy for EAS Hosting web deployments

Introduced 2026-04-22 · score 0.91

HOW TO USE IT

When a build-tools workflow deploys a web app to EAS Hosting, add an `eas/deploy` step after export. The step runs the deployment and exposes deployment output values to later steps.

steps: - uses: eas/export - uses: eas/deploy id: deploy

WHY THIS HELPS

Deploy a web app to EAS Hosting from a build-tools workflow.

REQUIREMENTS AND LIMITATIONS

  • Version: v18.8.0
  • uses: eas/deploy (required): Runs the EAS Hosting deployment function in a workflow step.
  • id: Assigns the step identifier used to read its outputs, as in `${{ steps.deploy.outputs.deploy_url }}`.
  • deploy_json, deploy_url, deploy_deployment_url, deploy_identifier, deploy_dashboard_url, deploy_alias_url: Documented step outputs; the PR example maps them to job outputs for later steps or jobs.
  • Prerequisite: The example uses a `type: custom` job and includes `eas/checkout`, `eas/use_npm_token`, `eas/install_node_modules`, and `eas/export` before `eas/deploy`. The PR's failure example omits setup steps and is expected to fail.
  • Prerequisite: The PR describes `eas/deploy` as streamlining the usual export-plus-deploy combination; its example explicitly runs `eas/export` before `eas/deploy`.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card