菜单
Publish an OTA update with eoas (not EAS). Use when the user has EOO_TOKEN, needs `npx eoas publish --branch …`, or must map a dashboard channel to that branch.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/mercuretechnologies/xprem --skill xprem-publish命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | xprem-publish |
| description | Publish an OTA update with eoas (not EAS). Use when the user has EOO_TOKEN, needs `npx eoas publish --branch …`, or must map a dashboard channel to that branch. |
Read the live docs. Do not invent flags and do not confuse this with eas update.
https://mercure-technologies.gitbook.io/xprem/~gitbook/mcp), orUse eoas only. Never run eas update / EAS Update unless the user explicitly wants Expo's hosted service instead of xprem.
eoas init) — otherwise xprem-configure-expoEOO_TOKEN, pick a branch, or point a channel at that branchEOO_TOKEN is the app-scoped API key created in the dashboard. Set it in the process environment. EOAS does not load .env files (expo export runs with EXPO_NO_DOTENV=1).
Without EOO_TOKEN, EOAS silently falls back to Expo authentication and the xprem server rejects the publish.
From the Expo project (example from the live quickstart / publish page):
export RELEASE_CHANNEL=production
export EOO_TOKEN=eoo_your_api_key
npx eoas publish --branch production
--branch is required and is the only thing that selects the branch.RELEASE_CHANNEL does not select the branch; it is passed into app config / expo export so the JS bundle is built for that channel.runtimeVersion in app config. Re-read the live page before recommending Expo's fingerprint policy.Useful flags documented on the live page (re-read before using): --platform, --message / -m, --rollout-percentage, --nonInteractive (required in CI), --dumpSourcemap.
CI shape from the docs:
EOO_TOKEN=$EOO_TOKEN RELEASE_CHANNEL=production \
npx eoas publish --branch production --nonInteractive
eoas publish refuses a dirty git tree (untracked files count). --nonInteractive aborts with Commit all changes. Aborting.... Escape hatches on the live page: --disableRepositoryCheck or EAS_NO_VCS.
A build is bound to a channel; an update is published to a branch. In the dashboard: Channels → Create Channel and attach it to the branch you just published. A fresh channel serves that one branch. Use the channel baked into the Expo build, not a guessed default.
Do not invent auto-rollback. Progressive rollouts use --rollout-percentage plus dashboard controls; if asked, read Progressive rollouts.
Wire an Expo app to a running xprem server. Use when the user needs the signing certificate (certs/certificate.pem), App ID, npx eoas init, updates.url / request headers, or a release channel on a native build. Not for publishing an update (use xprem-publish).
Connect Cursor or another MCP client to a deployed xprem control plane at https://<host>/mcp. Use when the user wants an agent to list apps, branches, channels or updates, or to rollback/republish on their own server. Not for the public docs MCP (already bundled).
Stand up a working xprem server in minutes. Use when the user wants a first Railway or local Docker+Postgres deploy, dashboard login, or the first admin account. Not for Helm, S3/CDN, Observe, or production hardening.
