{"id":"org_m4ShHtUXoJ67paiOEYqFS","slug":"expo","name":"Expo","domain":"expo.dev","description":null,"category":"framework","tags":["android","ios","mobile","react-native"],"sourceCount":3,"releaseCount":176,"releasesLast30Days":5,"avgReleasesPerWeek":1.7,"lastFetchedAt":"2026-04-19T07:02:06.598Z","trackingSince":"2023-08-09T06:29:07.000Z","aliases":[],"accounts":[{"platform":"github","handle":"expo"}],"products":[],"sources":[{"id":"src_wVgVE1H9ZBSPx9XDdBVSU","slug":"eas-cli","name":"EAS CLI","type":"github","url":"https://github.com/expo/eas-cli","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":102,"latestVersion":"v18.7.0","latestDate":"2026-04-14T18:51:00.000Z","latestAddedAt":"2026-04-14T23:04:14.551Z","productSlug":null,"productName":null},{"id":"src_Rp_lS4O8RgwNh_yHBA-O7","slug":"expo-changelog","name":"Expo Changelog","type":"feed","url":"https://expo.dev/changelog","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":50,"latestVersion":null,"latestDate":"2026-03-04T16:30:00.000Z","latestAddedAt":"2026-04-08T00:02:18.347Z","productSlug":null,"productName":null},{"id":"src_Q4traE3J_xq6Ty02_9KqR","slug":"expo-orbit","name":"Expo Orbit","type":"github","url":"https://github.com/expo/orbit","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":24,"latestVersion":"expo-orbit-v2.5.0","latestDate":"2026-04-02T21:07:11.000Z","latestAddedAt":"2026-04-08T00:00:45.566Z","productSlug":null,"productName":null}],"overview":{"scope":"org","content":"**EAS CLI now tracks build performance via Expo Observe, adds App Store metadata tooling, and requires Node 20+.**\n\n**Expo Observe ships for production performance monitoring.** EAS added `observe:metrics`, `observe:events`, and `observe:versions` commands (v18.6.0) to surface real-world app performance data—launch times, device breakdowns, update impact—addressing a gap in React Native debugging that existed only at development time.\n\n**App Store metadata and App Clip support expanded.** The CLI gained comprehensive Apple metadata handling: age ratings, content descriptions, App Clip bundle identifiers for multi-target builds, and full `metadata:push`/`metadata:pull` sync including per-locale subtitles, header images, and review invocation URLs (v18.5.0–v18.6.0). Non-interactive mode with ASC API Key auth lets CI workflows manage store metadata without prompts.\n\n**Build and workflow automation via MCP for AI assistants.** EAS exposed `build_info`, `build_list`, `build_logs`, `build_run`, `build_cancel`, and `build_submit` tools through the Expo MCP Server, letting Claude, Cursor, and VS Code extensions trigger builds and check status directly from AI-assisted dev workflows (Feb 2026).\n\n**Compiler caching landed for 30% faster builds.** Both Android and iOS builds now support ccache-backed compiler caching via `EAS_USE_CACHE` and related env vars, storing `.o` files and native library compilation results across builds at no extra cost (Jan 2026).\n\n**Breaking: Node 18/19 dropped; `--environment` required for SDK 55+ updates.** v18.0.1 enforces Node 20+. v18.0.5 made `--environment` mandatory for `eas update` when targeting SDK 55, aligned with new update infrastructure.\n\n**Build ergonomics tightened.** Added `--skip-bundler` and `--skip-build-if-not-found` flags to `eas build:dev` for faster iteration. Auto-detection of CI/non-TTY environments now enables `--non-interactive` without explicit flags. Android keystore auto-generation in non-interactive mode eliminated friction. Browser-based login via `--browser` flag replaced direct terminal auth; `--non-interactive` now auto-enables with `--json` output (v18.0.3–v18.2.0).\n\n**Orbit gains platform coverage.** macOS and watchOS app launching, SF Symbols on macOS, improved iOS simulator reliability, and deep-link crash fixes rounded out device support. Upgraded to Expo SDK 54 and React Native 0.81.","releaseCount":22,"lastContributingReleaseAt":"2026-04-14T18:51:00.000Z","generatedAt":"2026-04-16T15:16:20.745Z","updatedAt":"2026-04-16T15:16:20.745Z"},"knowledgePage":{"scope":"org","content":"**EAS CLI now tracks build performance via Expo Observe, adds App Store metadata tooling, and requires Node 20+.**\n\n**Expo Observe ships for production performance monitoring.** EAS added `observe:metrics`, `observe:events`, and `observe:versions` commands (v18.6.0) to surface real-world app performance data—launch times, device breakdowns, update impact—addressing a gap in React Native debugging that existed only at development time.\n\n**App Store metadata and App Clip support expanded.** The CLI gained comprehensive Apple metadata handling: age ratings, content descriptions, App Clip bundle identifiers for multi-target builds, and full `metadata:push`/`metadata:pull` sync including per-locale subtitles, header images, and review invocation URLs (v18.5.0–v18.6.0). Non-interactive mode with ASC API Key auth lets CI workflows manage store metadata without prompts.\n\n**Build and workflow automation via MCP for AI assistants.** EAS exposed `build_info`, `build_list`, `build_logs`, `build_run`, `build_cancel`, and `build_submit` tools through the Expo MCP Server, letting Claude, Cursor, and VS Code extensions trigger builds and check status directly from AI-assisted dev workflows (Feb 2026).\n\n**Compiler caching landed for 30% faster builds.** Both Android and iOS builds now support ccache-backed compiler caching via `EAS_USE_CACHE` and related env vars, storing `.o` files and native library compilation results across builds at no extra cost (Jan 2026).\n\n**Breaking: Node 18/19 dropped; `--environment` required for SDK 55+ updates.** v18.0.1 enforces Node 20+. v18.0.5 made `--environment` mandatory for `eas update` when targeting SDK 55, aligned with new update infrastructure.\n\n**Build ergonomics tightened.** Added `--skip-bundler` and `--skip-build-if-not-found` flags to `eas build:dev` for faster iteration. Auto-detection of CI/non-TTY environments now enables `--non-interactive` without explicit flags. Android keystore auto-generation in non-interactive mode eliminated friction. Browser-based login via `--browser` flag replaced direct terminal auth; `--non-interactive` now auto-enables with `--json` output (v18.0.3–v18.2.0).\n\n**Orbit gains platform coverage.** macOS and watchOS app launching, SF Symbols on macOS, improved iOS simulator reliability, and deep-link crash fixes rounded out device support. Upgraded to Expo SDK 54 and React Native 0.81.","releaseCount":22,"lastContributingReleaseAt":"2026-04-14T18:51:00.000Z","generatedAt":"2026-04-16T15:16:20.745Z","updatedAt":"2026-04-16T15:16:20.745Z"},"playbook":{"scope":"playbook","content":"# Expo — Playbook\n\n> Agent reference for fetching and maintaining **Expo** (`expo`) changelog sources.\n\n**3** active sources · domain: expo.dev\n\n## Sources\n\n| Name | ID | Type | URL | Last Fetched |\n|------|-----|------|-----|--------------|\n| Expo Changelog | `src_Rp_lS4O8RgwNh_yHBA-O7` | feed | https://expo.dev/changelog | Apr 18 |\n| EAS CLI | `src_wVgVE1H9ZBSPx9XDdBVSU` | github | https://github.com/expo/eas-cli | Apr 18 |\n| Expo Orbit | `src_Q4traE3J_xq6Ty02_9KqR` | github | https://github.com/expo/orbit | Apr 18 |\n\n## Agent Notes\n\n### Extraction patterns\n\n**EAS CLI (`eas-cli`, github)**\n- Version format: semver with `v` prefix (e.g., `v18.5.0`, `v18.0.6`, `v16.32.0`). Patch versions are common (v18.0.1 through v18.0.6 observed). The jump from v16.x to v18.x indicates major versions can skip numbers.\n- Cadence: ~1.4 releases/week average. In March 2026: 4 releases (v18.1.0 through v18.4.0). February 2026: 5 releases (v18.0.1 through v18.0.6). October 2025: 6 releases. Active development with steady output.\n- Content structure: Titles match version (`v18.5.0`). Release body uses emoji-prefixed section headers: New features, Bug fixes, Breaking changes, Chores. Each item is a bullet with PR link and author attribution.\n- All 100 tracked releases have content, dates, and versions. No data quality issues observed.\n- Some patch releases have minimal/empty bodies (e.g., v18.0.6 has just the version number and no changelog entries).\n\n**Expo Changelog (`expo-changelog`, scrape/feed)**\n- Version format: almost entirely null. Only 1 of the 20 most recent releases has a version (`0.80` for \"Expo support for React Native 0.80\"). This source tracks product announcements, not versioned software releases.\n- Cadence: ~0.4 releases/week (roughly 2/month). March 2026: 2 entries. February 2026: 2 entries. January 2026: 2 entries. Slower cadence reflects announcement-style content.\n- Content quality issue: many releases have empty or very short `content` fields. Examples with empty content: \"MCP tools for EAS Build and Workflows\", \"Mitigating Multiple Security Vulnerabilities in React Server Components\", \"Require Two-Factor Authentication for Organization Members\", \"Expo support for React Native 0.80\". The RSS feed provides only summaries, not full article content. Full content lives on the expo.dev/changelog pages and would require scrape enrichment.\n- Feed URL: `https://expo.dev/changelog/rss.xml` (type listed as \"unknown\", but functioning). Feed has ETag support (`feedEtag` present), enabling change detection.\n- Only fetched once successfully (50 releases inserted on 2026-04-08). The `changeDetectedAt` field is set (2026-04-10), indicating the cron detected upstream changes, but no subsequent fetch has occurred -- this may need a manual `fetch --changed` to pick up new entries.\n\n**Expo Orbit (`expo-orbit`, github)**\n- Version format: prefixed semver as `expo-orbit-v2.5.0`, `expo-orbit-v2.4.0`, etc. The `expo-orbit-` prefix is part of the GitHub release tag. Titles are cleaner: just `v2.5.0`.\n- Cadence: ~0.2 releases/week. Much slower than EAS CLI. 3 releases in last 30 days (March-April 2026 burst: v2.3.0, v2.4.0, v2.5.0). Before that, a 5-month gap between v2.1.0 (June 2025) and v2.2.0 (November 2025). Releases are bursty, not regular.\n- Content structure: Same emoji-prefixed sections as EAS CLI (New features, Bug fixes, Others). Note the \"Others\" category differs from EAS CLI's \"Chores\".\n- 24 total releases tracked, going back to August 2023. All have content and dates. No data quality issues.\n- Primarily maintained by a single contributor (@gabrieldonadel).\n\n### Known quirks\n\n- **expo-changelog feed content is thin**: The RSS feed at `expo.dev/changelog/rss.xml` delivers summaries only. Multiple releases have completely empty content fields. Enrichment via scrape would significantly improve data quality for this source. Consider running `enrich expo-changelog` to backfill full article content from the individual changelog page URLs.\n- **expo-changelog has stale data**: Despite `changeDetectedAt` being set (indicating upstream changes detected by cron polling), the source has only been fetched once (2026-04-08). New entries since then are not yet ingested.\n- **expo-orbit version tags include product prefix**: Versions are stored as `expo-orbit-v2.5.0` rather than just `v2.5.0`. This is a GitHub tagging convention for the monorepo-adjacent release pattern. Titles correctly strip the prefix.\n- **EAS CLI empty patch releases**: Some patch versions (e.g., v18.0.6) have no changelog body -- just the version string. These appear to be silent/internal releases.\n- **No primary source set**: None of the 3 sources has `isPrimary: true`. Consider designating expo-changelog as primary since it covers the broadest product scope.\n\n### Source coverage\n\n- **EAS CLI** covers the Expo Application Services CLI tool -- build, submit, update, and workflow commands. High-frequency, well-structured GitHub releases. 100 releases tracked. Good coverage.\n- **Expo Changelog** covers the official product changelog at expo.dev -- SDK releases, platform features, service announcements, and security advisories. 50 releases tracked. Content quality is degraded due to feed-only ingestion (summaries, not full articles). This is the most important source for understanding Expo platform changes but needs enrichment.\n- **Expo Orbit** covers the macOS/desktop menu-bar companion app for managing simulators and devices. 24 releases tracked. Niche but well-structured.\n- **Missing coverage**: The main `expo/expo` GitHub repo (the SDK monorepo) is not tracked as a separate source. SDK releases appear in expo-changelog but without full content. The `expo-go` app releases are also not tracked separately. Consider adding `https://github.com/expo/expo` for SDK-level release tracking if more granular version data is needed.\n","updatedAt":"2026-04-18T20:42:44.504Z"}}