expo-cicd-workflows

EAS workflow files live in .eas/workflows/ as .yml or .yaml files with top-level name, on, and jobs keys. Fetch the official schema from api.expo.dev to get current job types and required parameters before writing the file.

Run the validate.js script with Node.js, passing one or more workflow file paths. It fetches the latest schema from api.expo.dev, compiles it with Ajv, and reports each error with its path and allowed values.

Supported triggers, job types, runner types, and VM images are defined in the official JSON schema at api.expo.dev/v2/workflows/schema. Fetch the schema rather than relying on memorized values, since options evolve as features are added.

EAS workflows support ${{ }} expressions with github, inputs, needs, jobs, steps, and workflow contexts. These provide access to repository events, workflow_dispatch inputs, dependent job outputs, and workflow metadata.

Validation fails when required fields for a job type are missing, needs or after reference nonexistent jobs, or expressions use invalid contexts. The validator prints each error path with the allowed values so you can fix them directly.