Commit Graph
78 Commits
Author SHA1 Message Date
Ash Wu 62ddc91aa4 [build-tools] stop logging workflow hook parsing in build logs (#4717)
Hook parsing in native builds runs between READ_PACKAGE_JSON and
INSTALL_DEPENDENCIES and logged through the phase-less logger, so every
native build with hooks showed an "Unknown build phase" log group.
Ignore unknown and unrun hook keys silently in both the native and the
steps parser, let the eas/checkout step print the working-directory line
itself, and drop the after-hook failure line that the failing hook step
already logs.
2026-10-22 21:56:13 +08:00
Expo CI 44b63e5a7d v25.3.0 2026-10-20 19:17:05 +00:00
Expo CI e61a563b70 v25.2.0 2026-10-17 23:23:01 +00:00
Expo CI aa9f5370d4 v25.1.1 2026-10-16 21:35:07 +00:00
Expo CI c8aa5eb05d v25.1.0 2026-10-16 19:51:06 +00:00
Expo CI 785cfe2d53 v25.0.0 2026-10-15 22:42:24 +00:00
Expo CI 34e8b45bad v24.13.0 2026-10-12 17:44:06 +00:00
Douglas LowderandClaude Opus 5.5 bb98f5beef [eas-cli][local-build-plugin] Deprecate Node 20, use Node 22 in CI (#4579)
* [eas-cli][local-build-plugin] Deprecate Node 20, use Node 22 in CI

Print a deprecation warning from the eas-cli and local-build-plugin
bin scripts when running on Node.js < 22. Develop and test on Node.js
22: bump mise, drop 20.18.3 from the test matrix, and move to
@tsconfig/node22 and @types/node 22. Published engines are unchanged.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-11 15:45:17 -07:00
Expo CI 86b85e7d8d v24.9.0 2026-10-02 17:32:47 +00:00
Expo CI 9eefd5a5c4 v24.8.0 2026-09-24 21:13:58 +00:00
Will Schurman 🦦 3bb4240cb4 Upgrade typescript to 6.x (#4400)
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->

# Why

Follow-up to #4399 to upgrade typescript to latest version. 

# How

Tell claude to upgrade to 6.x.

# Test Plan

CI, tests
2026-09-17 11:51:16 -07:00
Will Schurman 🦦 1677efc00c Upgrade typescript to highest 5.x (#4399)
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->

# Why

This is a bit behind in typescript. 6.x is where most of our repos live.

First step is to get to highest 5.x.

# How

Tell claude to upgrade to highest 5.x.

It required a new version of `https-proxy-agent` to be compatible with new node types.

# Test Plan

`yarn start`, tests.
2026-09-17 10:17:45 -07:00
Expo CI 43068db22a v24.5.0 2026-09-15 09:41:35 +00:00
Expo CI 66cdccb0e7 v24.3.0 2026-09-11 12:31:21 +00:00
Expo CI 97553334d4 v24.2.0 2026-09-11 10:52:46 +00:00
Expo CI 5409c03d58 v24.0.0 2026-09-09 20:07:38 +00:00
Expo CI 0658d58efd v23.1.0 2026-08-31 11:24:34 +00:00
Brent Vatne add787f625 [local-build-plugin] Replace bunyan with @expo/bunyan (#4284)
* [local-build-plugin] Replace bunyan with @expo/bunyan

* Update changelog for @expo/bunyan
2026-08-28 15:45:28 -07:00
Brent Vatne ec2c2aca5e [steps] Replace lodash.get with a local helper (#4283)
* [steps] Replace lodash.get with a local helper

* Update changelog for lodash.get removal
2026-08-28 15:45:28 -07:00
Brent Vatne 1e86c48f48 [eas-cli][steps] Bump uuid to v11 (#4282)
* [eas-cli][steps] Bump uuid to v11

* Update changelog for uuid v11
2026-08-28 15:45:27 -07:00
Expo CI 2e2aaa4ac9 v23.0.0 2026-08-28 11:15:00 +00:00
Expo CI 39c39ad4bf v22.4.0 2026-08-24 21:35:36 +00:00
Szymon Świerk 16d234b11d [steps] Report a broken composite if: on the call, not an inner step (#4216)
* [steps] Report a broken composite if: on the call, not an inner step

* [steps] Simplify condition evaluation error handling by building the erro message in the error constructor
2026-08-24 18:52:39 +02:00
Expo CI 3f4ed25bb9 v22.1.0 2026-08-20 14:15:53 +00:00
Szymon Świerk 1f4c1edd99 [steps] Composite functions: skip the outputs step when the call never ran (#4207)
* [steps] Composite functions: skip the outputs step when the call never ran

* [steps] test coverage improvement: recursive anyAuthoredChildExecuted when a nested call has no outputs
2026-08-17 13:40:32 +02:00
Expo CI b92a9cc5a7 v22.0.0 2026-08-14 14:24:53 +00:00
Expo CI 60032049ec v21.7.1 2026-08-10 15:44:17 +00:00
Pieter Willekens c93614ec55 [steps][create-eas-build-function] Declare missing dependencies (#3798)
`fast-glob` and `arg` were imported but not declared in their packages,
resolving only via workspace hoisting. Declare them explicitly so the
packages keep working when installed standalone.
2026-08-10 13:15:28 +02:00
Expo CI 866febb1ba v21.6.0 2026-08-05 23:02:14 +00:00
Szymon Świerk 86fc9ebb80 [eas-cli][build-tools][steps] Validate local composite functions referenced from workflow hooks; extract the shared loader into steps (#4064)
* [eas-cli] Validate local composite functions referenced from workflow hooks

* extract the local composite function loader into @expo/steps

* skip validation when project_root_directory is set

* Validate defaults.hooks and remove project_root_directory skip
2026-08-05 14:29:44 +02:00
Expo CI b27fe84a1e v21.5.0 2026-08-03 19:10:13 +00:00
Szymon Świerk 56943702e3 [build-tools][steps] Load composite function catalogs for hook steps (#4063)
* [build-tools] Load composite function catalogs for hook steps

* do lazy loading of composite functions in hooks

* report the hook key on composite function load errors

* validate hook step functions only for reached anchors

* cleanup hook key parsing

* warn on unknown hook key

* share one composite function catalog across hook keys

* report the hook key on all composite step config errors

* report the hook key on composite expansion errors
2026-08-03 13:57:52 +02:00
Szymon Świerk a6ce70e46f [steps] Support local composite functions in hook steps (#4062)
# Why

Hook steps currently reject `uses: ./...` local composite functions. Users should be able to reuse the same composites in hooks as in the main workflow.

# How

A composite function used in a hook is expanded into its inner steps at parse time, the same way it is in the main workflow, and the whole expansion becomes a single hook entry. The step's `if:` gates the expansion as a whole.

Hook construction now takes a catalog of composite functions. Without it, referencing a composite fails with a missing-function error instead of the previous "not supported in hooks" error.

Wiring reading the composite functions files will be added in follow-up PRs in the stack.

# Test Plan

Added unit tests.
2026-07-30 18:11:54 +02:00
Szymon Świerk ee03114095 [steps] Unify the default gating of steps with no if: across steps, composite scopes, and hooks (#4061)
# Why

For a step with no `if:`, whether the step should run was decided in 3 separate places: `BuildStep.shouldExecuteStep`, the composite function scope (same rule), and the hook executor (its own rule). That bypass means composite scopes never see hook defaults, which is a blocker for adding support for composite functions in hooks.

# How

A single gate now decides whether any step runs, taking a single input: a bool telling whether a step with no `if:` should run. Composite functions called from hooks therefore inherit the hook's rule. Steps with an explicit `if:` are unaffected.

Behavior-preserving refactor.

# Test Plan

- Existing steps/hook tests still pass.
- Added unit coverage for the run-by-default value on `shouldExecuteStep` /
  `isActive`, and hook sibling skip/continue cases for the before/after defaults.
2026-07-30 17:42:46 +02:00
Szymon Świerk 2e00719193 [build-tools] Load local composite function catalog at build runtime (#3930)
# Why

This PR stack adds local composite functions for EAS workflows (`uses: ./.eas/functions/...`). Earlier PRs define the schema, expand calls into steps, and wire inputs/outputs. The build runtime still needs to load those `function.yml` files from the project and pass them into `StepsConfigParser`.

This PR is the I/O layer: discover referenced local composite functions on disk, validate them, and hand the catalog to the parser for custom builds and generic jobs.

# How

- Adds catalog helpers in `@expo/steps` (`buildCompositeFunctionCatalogFromStepsAsync`, `resolveLocalCompositeFunctionPath`)
- Adds `packages/build-tools/src/steps/compositeFunctions.ts` to resolve paths relative to the EAS project root, read `function.yml` / `function.yaml`, and validate with `CompositeFunctionConfigZ`
- Wires the catalog into `runCustomBuildAsync` and `runGenericJobAsync`

# Test Plan

Added unit tests for catalog loading and custom-build parse integration.
2026-07-29 11:25:34 +02:00
Expo CI dcc7201ca8 v21.4.0 2026-07-28 10:18:26 +00:00
Expo CI 3784a50399 v21.3.0 2026-07-27 01:58:10 +00:00
Szymon Świerk 68c87fa6fb [steps][4/4] Resolve composite function outputs (#4015)
# Why

This PR stack adds local composite functions for EAS workflows. A `function.yml` declares `outputs:` with templated values, and the caller should read them as `${{ steps.setup.outputs.version }}`, where `setup` is the id of the calling step.

After the previous PRs, data flows into a composite function (inputs, env) but nothing flows back out. This PR closes that loop.

# How

For a composite function that declares `outputs:`, `CompositeFunctionExpander` appends a synthetic function step after the inner steps, reusing the caller's step id.

- The step runs with `if: ${{ always() }}`
- Output values are interpolated against the composite-function-local step namespace

# Test Plan

Added outputs unit tests.
2026-07-24 17:31:29 +02:00
Szymon Świerk 1010e3b997 [steps][3/4] Interpolate composite function inputs (#4014)
# Why

This PR stack adds support for local composite functions in workflows. After structural expansion, inner steps still could not see `${{ inputs.* }}`, and caller `env` did not yet reach them at runtime.

This PR adds the data layer: input declaration, validation and interpolation, and runtime resolution of the caller context (env, templated working directories).

# How

- `CompositeFunctionExpander` builds declared composite function inputs as real `BuildStepInput` instances
- `BuildStepCompositeFunctionScope` exposes `${{ inputs.* }}` as lazy getters
- Caller `env` and working directory templating resolve through the composite function scope

# Test Plan

Added inputs and scoping unit tests.
2026-07-24 17:14:56 +02:00
Szymon Świerk a8e8c796dd [steps][2/4] Expand composite function references into build steps (#3929)
# Why

EAS workflows need reusable local composite functions: a step like `uses: ./.eas/functions/setup` should run the steps defined in `function.yml`, not be treated as a built-in function.

This PR adds the structural layer for that: turning a composite function call into concrete workflow steps with correct ids, scoping, and control flow. Input interpolation, outputs, and loading `function.yml` from disk are handled in separate PRs.

# How

When `StepsConfigParser` sees a local `uses:` path (`./` or `../`), `CompositeFunctionExpander` replaces the call with a flat list of inner steps:

- ID namespacing: inner step `read` under caller `setup` becomes `setup__read`
- Each expanded step carries a `BuildStepCompositeFunctionScope` so `${{ steps.* }}` and `${{ inputs.* }}` resolve against composite-function-local names
- Nested local composite functions are expanded recursively with cycle and depth checks
- Local composite functions are rejected in hooks

# Test Plan

Added expansion unit tests covering nesting, cycles, depth limits, and id collisions.
2026-07-24 16:56:35 +02:00
Szymon Świerk fcea341834 [steps][1/4] Add isCompositeFunctionPath and reject local composite functions in custom builds (#3956)
# Why

Local composite functions use `uses: ./...` paths. Custom build configs (`.eas/build/*.yml`) must reject these early with a clear error.

# How

- Adds `isCompositeFunctionPath` in `localCompositeFunctions.ts`
- Rejects local composite function paths in `validateAllFunctionsExist` for custom builds

# Test Plan

Added unit tests.
2026-07-24 16:37:24 +02:00
Expo CI 24272d8a5f v21.1.0 2026-07-22 23:12:02 +00:00
Expo CI 62d46fece5 v21.0.3 2026-07-22 12:31:49 +00:00
Expo CI e9ebc41413 v21.0.2 2026-07-17 06:00:55 +00:00
Ash Wu d14c0b196b [eas-build-job] internal refactor general hook (#4023)
Signed-off-by: Ash Wu <[email protected]>
2026-07-16 19:59:08 +08:00
Expo CI a62289b988 v21.0.1 2026-07-15 06:42:00 +00:00
Ash Wu f448bc75b5 [build-tools] unify workflows hook (#3957)
* [eas-build-job] Add hook anchors registry and step stamp fields

Signed-off-by: Ash Wu <[email protected]>

* [steps] Add hook insertion, after-hook gate, and source function retention

Signed-off-by: Ash Wu <[email protected]>

* [build-tools] Pass job hooks into the steps parser

Signed-off-by: Ash Wu <[email protected]>

* address comments

Signed-off-by: Ash Wu <[email protected]>

---------

Signed-off-by: Ash Wu <[email protected]>
2026-07-14 15:31:11 +08:00
Expo CI c72cee372f v21.0.0 2026-07-13 17:21:41 +00:00
Szymon Dziedzic 69024620f9 Bump cross-spawn in steps fixture (#3977)
* Bump cross-spawn in steps fixture

* Add changelog entry for cross-spawn bump
2026-07-13 14:51:04 +02:00
Expo CI cd47185f29 v20.5.1 2026-07-01 16:34:31 +00:00