expo-cicd-workflows

You validate Expo EAS workflow YAML files by running a validation script against your file path. The skill applies schema-driven validation using the official Expo workflow JSON schema to verify job types, triggers, and required fields before you commit.

An Expo EAS workflow is a YAML configuration file located in `.eas/workflows/*.yml` that defines CI/CD automation for Expo projects. You need to define one to configure triggers and jobs for tasks like building and testing your application.

You create a deployment pipeline by authoring YAML files in the `.eas/workflows` directory. Using guided workflow authoring references and examples, you define distinct build and test jobs, then validate the workflow definitions to ensure accuracy before committing.

Yes, EAS CI/CD workflow validation supports standard YAML formats. It relies on dependencies like `js-yaml` for parsing and `ajv` with `ajv-formats` to apply the official Expo workflow JSON schema for robust verification.

Your Expo EAS workflow YAML fails validation when it contains incorrect job types, missing required fields, or invalid trigger configurations. The schema-driven validation checks your file against the official Expo workflow JSON schema to pinpoint these errors.