* [eas-cli] Prompt for account when linking unconfigured project
* [eas-cli] Update CHANGELOG
* [eas-cli] Sort account choices from newest to oldest in project link prompt
* [eas-cli] Revert account sorting by creation date in project link prompt
# Why
New server code for observe features may throw errors when a feature is not available for an account.
# How
Handle these errors correctly, and surface the correct server-side error message.
# Test Plan
- Testing against accounts in staging
- New unit tests added
# 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.
# 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.
# 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.
# 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.
# Why
First step toward local composite functions for EAS Workflows: reusable step groups referenced via `uses:` in `.eas/workflows/*.yml`.
This PR adds the shared contract in `@expo/eas-build-job` so all consumers agree on composite function config shape.
# How
Introduce the composite function config schema in `@expo/eas-build-job`, the single source of truth for the shape of a `function.yml` file. No runtime behavior changes yet.
Added:
- `CompositeFunctionConfigZ` / `CompositeFunctionConfig`: Zod schema and type for `function.yml` (inputs, outputs, runs.steps)
- `CompositeFunctionCatalog`: map of normalized path → config
# Test Plan
Added unit tests for `CompositeFunctionConfigZ`.
- security.md: restore the dropped "## What NOT to flag" heading (the
don't-flag bullets were dangling under the trust-boundary section).
- correctness.md: flag cross-package/compat breakage — breaking changes to
@expo/eas-build-job Job types/schemas, shared signature changes a sibling
relies on, and GraphQL contract changes landing before the server side.
- consistency.md: flag new behavior shipped without a test (memfs/nock/
ts-mockito harness), and missing/malformed CHANGELOG entries.
- shared.md: ground judgment in the per-package CLAUDE.md, not just a pointer
to the root AGENTS.md.
- ECR_VERSION default ^0.2.0 -> ^0.2.1 (fuzzy quote-grounding + escalate-on-absence,
so real findings with imperfect quotes are no longer silently dropped).
- shared.md: ask for one contiguous verbatim line and drop the "evidence not found
-> discarded" threat, matching the engine's softened grounding behavior.
The bare npx form works (npm picks the first bin) but relies on multi-bin
auto-resolution; the explicit -p ... ecr form is guaranteed across npm
versions and matches the CI workflows.
# Why
`eas update` run inside an EAS Build 500s: it sends the build id as `turtleJobRunId`, which violates a job-run foreign key on the server.
Closes#3873.
# How
Only send `turtleJobRunId` when not running inside a build. Builds set `EAS_BUILD_PLATFORM` and job runs don't, so its presence tells them apart.
# Test Plan
Unit tests.
* [eas-cli] Prompt for platform in simulator:start instead of erroring
Make the --platform flag optional in `eas simulator:start`. When it is
omitted in interactive mode, show a platform selection dropdown instead
of throwing a missing-required-flag error. Non-interactive mode still
requires the flag and errors with a clear message.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
* update CHANGELOG.md
Co-Authored-By: Claude Opus 4.8 <[email protected]>
* [eas-cli] Address review feedback on simulator:start platform prompt
- Prompt for the platform before warning about overwriting an existing
session, so users aren't warned before they've picked a platform.
- Map the platform flag value to AppPlatform via an explicit exhaustive
record instead of a ternary that silently defaulted to iOS.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
---------
Co-authored-by: Claude Opus 4.8 <[email protected]>
# Why
EAS Workflows' `update` job is getting `before_update` / `after_update` hooks (ENG-25364). First concrete ask: uploading PostHog sourcemaps right after `eas update` publishes — sourcemaps only exist inside the job, and we don't want a vendor-specific step for every provider.
# How
`update` joins `HOOK_ANCHORS`. It is a stamp-only anchor: the server stamps `__hook_id: 'update'` on the update job's generated publish step (expo/universe#29311); no eas-cli function declares it.
# Test Plan
CI passes.
* [eas-cli] Add `eas env:set`, deprecate `env:create` and `env:update`
Introduce `eas env:set`, which creates or updates an environment
variable in a single command (upsert). `env:create` and `env:update`
now warn that they are deprecated in favor of `env:set` while keeping
their existing behavior for backwards compatibility.
* [eas-cli] Add `--json` to `eas env:set`, preserve file type on update
Look up the existing variable before resolving its value so updating a file
variable no longer requires re-passing `--type file`, mirroring the behavior
that `eas env:update` had. Also fix the `--value` flag description typo.
* [eas-cli] Preserve env memberships and hide deprecated commands
* [eas-cli] Remove redundant env:set comment
* [eas-cli] Align env:set flag names
* [eas-cli] Keep short env:set flags canonical
* [eas-cli] Preserve visibility in non-interactive env:set
* [eas-cli] Add hidden `eas chat` command
Ask the Expo dashboard AI assistant about your account and EAS projects from the terminal. Streams the reply, supports interactive multi-turn follow-ups, `--project`/`--account` scoping, `--non-interactive`, and `--json` for agent-friendly structured output.
Calls the website's `/api/chat` route using the CLI session secret; command is hidden while the backend feature gate rolls out.
* [eas-cli] Update changelog PR link for `eas chat`
* [eas-cli] Render markdown and steer output for `eas chat`
Render the streamed assistant reply as ANSI (bold, inline code, headings, bullets, links) one line at a time. Prepend a client-side system message steering the assistant to write terminal-friendly answers and include expo.dev links for referenced artifacts (builds, updates, etc.).
* [eas-cli] Add readline REPL with history and slash commands to `eas chat`
Replace the per-turn prompt with a reusable Node readline interface: arrow-key history across turns and /help, /clear, /exit slash commands, all in the normal scrolling buffer (no new dependency).
* [eas-cli] Fix `eas chat` interactive prompt exiting immediately
The ora spinner leaves stdin paused when it stops, so the readline prompt had nothing keeping the event loop alive and the process exited the moment the prompt appeared. Resume stdin before each prompt and stop the spinner from grabbing stdin (discardStdin: false).
* [eas-cli] Auto-scope `eas chat` to the current directory's project
When run inside a linked EAS project and neither --project nor --account is given, chat now focuses on that project automatically. Detection is silent and read-only: it never prompts, links, or creates a config, and falls back to account scope when the directory is not a linked project.
* [eas-cli] Seed `eas chat` history with the initial command-line message
The first message comes from argv, not the readline prompt, so Up-arrow had nothing to recall at the first follow-up. Pass it as readline's initial history.
* [eas-cli] Label and align `eas chat` speakers (Chat > / Expo >)
Prefix the assistant reply with a magenta "Expo > " label and indent its continuation lines to match, and label the user's turn "Chat > " (both 4-char names so the two align).
* [eas-cli] Wrap `eas chat` reply to terminal width and indent the spinner
Wrap each rendered line to the terminal width minus the indent (ANSI-aware, hard-breaking long URLs) and re-apply the indent to every wrapped piece, so terminal soft-wrapping no longer drops wrapped text to column 0. Also indent the ora spinner to align with the reply body.
* [eas-cli] Fix `eas chat` reply indent after spinner and reorder intro
The indented ora spinner leaves the cursor at its indent column when it stops (ora's clear() ends with cursorTo(indent)), which pushed the whole reply right by the indent. Reset the cursor to column 0 after stopping. Also move the commands hint above the echoed message and shorten it.
* [eas-cli] Render `eas chat` spinner with the Expo label prefix
Use ora's prefixText to show "Expo > <spinner> Thinking…" from the first frame instead of the indent option, which rendered unindented for a tick then snapped right. The spinner now reads as the reply and is cleared/replaced by the streamed text.
* [eas-cli] Decode `eas chat` stream with StringDecoder to avoid splitting multi-byte characters
* [eas-cli] Remove CHANGELOG entry for hidden `eas chat` command
* [eas-cli] Preserve chat context across follow-ups
* [eas-cli] Let `eas chat` open an interactive prompt with no message argument
* [eas-cli] Remove comments from `eas chat`
* [eas-cli] Keep `eas chat` interactive session alive when a request fails
In interactive mode, catch errors from the chat stream, print the message, and re-prompt instead of exiting the whole session. Single-shot and --json invocations still throw.
* [eas-cli] Keep `eas chat` spinner visible until the reply is ready to render
The spinner was cleared on the first text delta, but the line-buffered renderer only draws once a full line is buffered, leaving a blank gap. Stop the spinner lazily when the first visible line is written so the labeled loading indicator stays put until output appears.
* [eas-cli] Spell out abbreviated variable names in `eas chat`
rl -> readlineInterface, exp -> expoConfig, the *_RE markdown constants -> *_REGEX, and the repl test var -> replInput.
* [eas-cli] Simplify `eas chat` tool tracking and markdown renderer
Derive the toolCalls result from the assistant message parts instead of maintaining a second parallel map, and drop markdown constructs (headings, blockquotes, horizontal rules, italics) the system prompt tells the model not to emit.
* [eas-cli] Sanitize streamed chat output
# Why
When session ID is omitted and the `observe:session` command is running interactively, walk the user through picking an event whose session they want to inspect. Non-interactive without a session ID still errors as before.
The goal is to support a flow similar to that already available on our website, where a user can select an event from a displayed list, and navigate to the session timeline that contains that event.
# How
Add new flags `--event-name` and `--sort-order`. If these are not provided, user will be prompted first to select from a list of event names (including custom events, if applicable), then select a sort order. The command also now takes the same time period flags as the other commands (`--days`, `--start`, `--end`).
Once the user has made the above selections, the user can choose from the list of events shown (up to 25), and the session for that event will be shown.
# Test Plan
- Tested manually with an SDK 57 project
- New unit tests added
* [eas-cli] Show accurate build overage count in pre-build usage warning
The overage count shown to paid users ("N builds beyond your included
credits") summed the value of every overageMetrics row, including rows
without build metadata (e.g. rollup/summary rows), which could inflate the
number. Filter to genuine per-worker build overage rows (those carrying
billingResourceClass + platform metadata) before summing.
Fetch that metadata on overageMetrics in the warning query so the rows can
be distinguished.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
* [eas-cli] Fix changelog PR reference for build overage warning entry
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
---------
Co-authored-by: Sarah Lane <[email protected]>
Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>