domains / families / devops / eas-workflows

eas-workflows

combined

Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation. Use when writing or reviewing Expo EAS workflow YAML: inspect current schema and job syntax, validate configuration, and separate draft edits from launching builds or submissions.

When to use

• Create or repair `.eas/workflows` YAML for an Expo application.
• Review triggers, dependencies, expressions or pre-packaged job parameters.
• Validate a proposed workflow without launching it or publishing an app.

When not to use

• Authenticated CLI validation is distinct from launching jobs; workflow runs, uploads, builds and store submissions need their actual authorized scope and account limits.
• Draft-2020-12 schema checks do not replace EAS server validation, profile references or expression-context checks.
• No unbounded fetch, arbitrary URL, redirect or secret is required to read the public references. On platforms without a no-follow cache-open flag, cached reads are skipped rather than following links.
• Does not replace environment-specific validation, testing, or maintainer review.

Skill page

Conflict

The expo/skills copy is the upstream procedure, but the sickn33 copy is not a simple reproduction: it adds security and operational constraints (Node 22+, exact-URL fetch allowlist, redirect rejection, 10-second deadline, 1 MiB response limit, 15-minute ETag cache, no-store handling, envelope data extraction, pinned local EAS CLI validation, and project trust checks) that the upstream copy lacks. It also disagrees with the upstream on whether `on` is required and on the expression contexts available. Crowning the upstream copy would hide these real alternative constraints and the conflicting schema interpretation.