expo-cicd-workflows

You can validate Expo EAS workflow YAML configurations by running the included scripts to verify schema compliance and correct syntax before committing your workflows. This enforces conformance for triggers, jobs, defaults, and contexts.

The best way to structure CI/CD pipelines for Expo builds and deployments is to apply workflow patterns to .eas/workflows/ files. This includes defining custom job types and safe triggers for previews and deployments.

To set up a new EAS workflow, follow the Quick Start instructions to author YAML files in your .eas/workflows/ directory. Use the provided fetch and validate scripts to verify schema compliance and syntax before committing.

Yes, you can use custom job types in Expo EAS workflows. The workflow patterns support custom job configurations across builds, previews, and deployments while enforcing schema conformance and safe use of triggers.

EAS workflow YAML fails schema validation when configurations contain incorrect syntax or violate official schema rules. Use the included validation scripts to identify misconfigurations in triggers, jobs, defaults, and contexts before committing.

You need YAML files to define EAS workflows and the EAS environment to execute them. The Skill uses js-yaml to parse configurations and ajv to validate them against the official schema, ensuring safe automation.