---
next_cursor: eyJzY29yZSI6MCwic2VxIjoxNTMxLCJzaW5jZSI6bnVsbCwidG9vbCI6ImVhcyIsInYiOjF9
has_more: true
next: https://sincecutoff.com/v1/changes.md?tool=eas&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxNTMxLCJzaW5jZSI6bnVsbCwidG9vbCI6ImVhcyIsInYiOjF9
items: 10
---
# sincecutoff.com changes: eas

## eas update adds bytecode and source map flags (eas, 2026-01-30)
Published 2026-10-19
- slug: eas-update-adds-bytecode-and-source-map-flags-c53f2b737d89
- score: 0.91

How to use it:

When publishing an update that needs bytecode disabled or source maps, pass the corresponding options to `eas update`. Use `--no-bytecode` to skip Hermes bytecode generation and `--source-maps inline` to embed source maps in the bundle.

Examples:

```
eas update --no-bytecode --source-maps inline
```

- why_it_matters: When publishing an update that needs bytecode or source map options, pass the corresponding flags to `eas update`.
- sources: <https://github.com/expo/eas-cli/releases/tag/v16.32.0>, <https://github.com/expo/eas-cli/pull/3339>, <https://docs.expo.dev/eas-update/getting-started/>
- gotchas: "Version: v16.32.0"; "--no-bytecode: Skips Hermes bytecode generation; the PR says it outputs plain JavaScript."; "--source-maps <mode>: Passes a source-map mode to Expo export. The PR documents `inline` as embedding source maps in the bundle. The flags are not documented as mutually exclusive."; "Prerequisite: Install EAS CLI and log in to an Expo account to publish updates."; "The source map mode syntax is not specified."; "Docs conflict: The release note names `--source-maps [mode]`; PR #3339 documents the flag and `inline` mode. No other mode values were verified."

## eas update:list filters by runtime version and platform (eas, 2026-01-30)
Published 2026-10-19
- slug: eas-update-list-filters-by-runtime-version-and-platform-a9542d5e1529
- score: 0.96

How to use it:

When inspecting published updates, use `--runtime-version` to filter by runtime version and `--platform` to filter by platform. Run `eas update:list` with either or both filters.

Examples:

```
eas update:list --runtime-version <runtime-version> --platform <android|ios|all>
```

- why_it_matters: When inspecting published updates for a project, narrow the update list by runtime version or platform.
- sources: <https://github.com/expo/eas-cli/releases/tag/v16.32.0>, <https://github.com/expo/eas-cli/blob/v16.32.0/packages/eas-cli/README.md>, <https://github.com/expo/eas-cli/blob/v16.32.0/packages/eas-cli/src/commands/update/list.ts>
- gotchas: "Version: v16.32.0"; "--runtime-version <value>: Filter updates by runtime version."; "--platform <android|ios|all>: Filter updates by platform. Alias: `-p`."; "Prerequisite: The command requires a project ID and a logged-in Expo account."

## eas login supports browser-based authentication (eas, 2026-02-12)
Published 2026-10-19
- slug: eas-login-supports-browser-based-authentication-d95fd30aa9f1
- score: 0.94

How to use it:

When the repository requires EAS access, run `eas login --browser` to log in to your Expo account using a browser.

Examples:

```
eas login --browser
```

- why_it_matters: Authenticate with EAS CLI while working in a repository that requires EAS access.
- sources: <https://github.com/expo/eas-cli/releases/tag/v18.0.1>, <https://github.com/expo/eas-cli/blob/v18.0.1/packages/eas-cli/README.md>
- gotchas: "Version: v18.0.1"; "--browser: Log in with a browser; v18.0.1 documents this flag. The release note says it was added to `eas login`."; "Prerequisite: Install EAS CLI; the v18.0.1 README documents `npm install -g eas-cli` or `yarn global add eas-cli`."

## eas update commands require --environment for SDK 55 and later (eas, 2026-02-25)
Published 2026-10-19
- slug: eas-update-commands-require-environment-for-sdk-55-and-later-d01d6ddb0d54
- score: 0.94

How to use it:

For projects using Expo SDK 55 or later, include `--environment` when running `eas update`. Choose the EAS environment whose variables the update should use.

Examples:

```
eas update --channel <channel-name> --message "<message>" --environment <environment-name>
```

- why_it_matters: Run an update command for a project using SDK 55 or later.
- sources: <https://github.com/expo/eas-cli/releases/tag/v18.0.5>, <https://docs.expo.dev/eas-update/getting-started/>, <https://docs.expo.dev/eas/cli/>
- gotchas: "Version: v18.0.5"; "--environment <value> (required): EAS environment used for server-side environment variables during command execution; examples include production, preview, and development."; "--channel <value>: Channel the published update should affect."; "--message <value>: Short message describing the update."; "Applies to update commands when SDK is 55 or later."

## eas commands with --json auto-enable --non-interactive (eas, 2026-03-09)
Published 2026-10-19
- slug: eas-commands-with-json-auto-enable-non-interactive-c00c80378b26
- score: 0.96

How to use it:

When running an EAS CLI command in an automated workflow, pass `--json` for JSON output; it also enables non-interactive mode. The command itself and any task-specific arguments depend on the operation.

Examples:

```
eas <command> --json
```

- why_it_matters: Run an eas command with JSON output in an automated workflow.
- before: Previously, users had to pass both `--json` and `--non-interactive` to request JSON output in non-interactive mode.
- sources: <https://github.com/expo/eas-cli/releases/tag/v18.2.0>, <https://docs.expo.dev/eas/cli/>, <https://github.com/expo/eas-cli/pull/3476>
- gotchas: "Version: v18.2.0"; "<command> (required): The EAS command for the task; choose from documented commands."; "--json: Enables JSON output and implies `--non-interactive`."; "--non-interactive: Runs the command in non-interactive mode. Passing `--json` implies this flag, so it need not also be passed."

## eas metadata:push and metadata:pull add non-interactive mode and ASC API Key authentication (eas, 2026-04-02)
Published 2026-10-19
- slug: eas-metadata-push-and-metadata-pull-add-non-interactive-mode-and-asc-api-key-aut-2d3d72f28fb8
- score: 0.91

How to use it:

When syncing iOS store metadata without prompts, use `eas metadata:push` to upload or `eas metadata:pull` to download and include `--non-interactive`. The v18.5.0 release adds ASC API Key authentication support for both commands.

Examples:

```
eas metadata:push --non-interactive
```

```
eas metadata:pull --non-interactive
```

- why_it_matters: When synchronizing app metadata without interactive prompts, run the metadata push or pull command with ASC API Key authentication configured.
- sources: <https://github.com/expo/eas-cli/releases/tag/v18.5.0>, <https://github.com/expo/eas-cli/blob/v18.5.0/packages/eas-cli/src/commands/metadata/push.ts>, <https://github.com/expo/eas-cli/blob/v18.5.0/packages/eas-cli/src/commands/metadata/pull.ts>
- gotchas: "Version: v18.5.0"; "--non-interactive: Run the command in non-interactive mode."; "-e, --profile <value>: Submit profile from eas.json; defaults to `production` if defined there."

## eas metadata:push and metadata:pull support screenshots and previews (eas, 2026-04-02)
Published 2026-10-19
- slug: eas-metadata-push-and-metadata-pull-support-screenshots-and-previews-fda80acb69ed
- score: 0.97

How to use it:

When syncing iOS App Store metadata for a repository, use `eas metadata:push` to upload the local store configuration, including screenshots and previews; use `eas metadata:pull` to generate it from the store. The commands support a submit profile and non-interactive mode.

Examples:

```
eas metadata:push [-e <profile>] [--non-interactive]
```

```
eas metadata:pull [-e <profile>] [--non-interactive]
```

- why_it_matters: When synchronizing app metadata for a repository, include screenshots and previews in the metadata transfer.
- sources: <https://github.com/expo/eas-cli/releases/tag/v18.5.0>, <https://docs.expo.dev/eas/cli/>, <https://docs.expo.dev/eas/metadata/getting-started/>
- gotchas: "Version: v18.5.0"; "-e, --profile=<value>: Submit profile from eas.json; defaults to `production` if defined there."; "--non-interactive: Run without interactive prompts."; "Prerequisite: EAS CLI installed; an Apple App Store app is required. EAS Metadata currently supports Apple App Store only."; "Prerequisite: Upload a new app binary and wait for it to be processed before pushing store configuration."

## eas build:dev supports --skip-bundler (eas, 2026-04-14)
Published 2026-10-19
- slug: eas-build-dev-supports-skip-bundler-dd03e168396d
- score: 0.96

How to use it:

When you want to install and run the development build without starting the bundler server, run `eas build:dev --skip-bundler`.

Examples:

```
eas build:dev --skip-bundler
```

- why_it_matters: Install and run a development build without starting the local Expo/Metro server.
- sources: <https://github.com/expo/eas-cli/releases/tag/v18.7.0>, <https://github.com/expo/eas-cli/blob/v18.7.0/packages/eas-cli/src/commands/build/dev.ts>
- gotchas: "Version: v18.7.0"; "--skip-bundler: Skip starting the bundler server; defaults to false."; "-p, --platform=<ios|android>: Select the iOS or Android platform."; "-e, --profile=<PROFILE_NAME>: Select the build profile from eas.json; it must allow emulator/simulator internal distribution development client builds. Defaults to `development-simulator`."; "Prerequisite: The selected build profile must allow emulator/simulator internal distribution development client builds."

## build-tools adds eas/deploy for EAS Hosting web deployments (eas, 2026-04-22)
Published 2026-10-19
- slug: build-tools-adds-eas-deploy-for-eas-hosting-web-deployments-eea3c4a892e6
- score: 0.91

How to use it:

When a build-tools workflow deploys a web app to EAS Hosting, add an `eas/deploy` step after export. The step runs the deployment and exposes deployment output values to later steps.

Examples:

```
steps:
  - uses: eas/export
  - uses: eas/deploy
    id: deploy
```

- why_it_matters: Deploy a web app to EAS Hosting from a build-tools workflow.
- sources: <https://github.com/expo/eas-cli/releases/tag/v18.8.0>, <https://github.com/expo/eas-cli/pull/3598>
- gotchas: "Version: v18.8.0"; "uses: eas/deploy (required): Runs the EAS Hosting deployment function in a workflow step."; "id: Assigns the step identifier used to read its outputs, as in `${{ steps.deploy.outputs.deploy_url }}`."; "deploy_json, deploy_url, deploy_deployment_url, deploy_identifier, deploy_dashboard_url, deploy_alias_url: Documented step outputs; the PR example maps them to job outputs for later steps or jobs."; "Prerequisite: The example uses a `type: custom` job and includes `eas/checkout`, `eas/use_npm_token`, `eas/install_node_modules`, and `eas/export` before `eas/deploy`. The PR's failure example omits setup steps and is expected to fail."; "Prerequisite: The PR describes `eas/deploy` as streamlining the usual export-plus-deploy combination; its example explicitly runs `eas/export` before `eas/deploy`."

## eas channel:insights reports channel runtime metrics (eas, 2026-04-22)
Published 2026-10-19
- slug: eas-channel-insights-reports-channel-runtime-metrics-546e6bb3eb41
- score: 0.96

How to use it:

When maintaining an app release, run channel insights for the target channel and runtime version to review adoption and crash metrics.

Examples:

```
eas channel:insights --channel <name> --runtime-version <version>
```

- why_it_matters: Review adoption and crash metrics for a channel and runtime version while maintaining an app release.
- sources: <https://github.com/expo/eas-cli/releases/tag/v18.8.0>, <https://github.com/expo/eas-cli/blob/v18.8.0/packages/eas-cli/src/commands/channel/insights.ts>
- gotchas: "Version: v18.8.0"; "--channel <name> (required): Name of the channel."; "--runtime-version <version> (required): Runtime version to query insights for."; "Prerequisite: Requires a logged-in user and an Expo project ID."

Next: https://sincecutoff.com/v1/changes.md?tool=eas&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxNTMxLCJzaW5jZSI6bnVsbCwidG9vbCI6ImVhcyIsInYiOjF9
Save `next_cursor`; next visit, pass it to get only what was published since.
<!-- end of page -->