메뉴
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에서 현재 제공할 수 있는 파일을 다운로드하세요.
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.
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.