* [build-tools] pass the website origin to serve-sim
* [build-tools] allow deploy previews to reach staging sessions
* [build-tools] allow the website dev ports on staging sessions
* [build-tools] tidy the website origin helper and its tests
* [build-tools] name only https website dev origins
* [eas-cli] Allow resolving an ASC API key without an issuer ID
* [eas-cli] Accept individual ASC API keys during authentication
* [eas-cli] Guard credential provisioning operations against individual ASC API keys
* [eas-cli] Allow individual ASC API keys for metadata and TestFlight setup
* [eas-cli] Accept individual ASC API keys in EAS Submit
* [eas-cli] Reject individual ASC API keys in the ASC integration flow
* [eas-cli] Update CHANGELOG for individual ASC API key support
* [eas-cli] Make eas simulator commands visible
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* [eas-cli] Add PR number to changelog entry
Co-Authored-By: Claude Fable 5.1 <[email protected]>
---------
Co-authored-by: Claude Fable 5.1 <[email protected]>
# Why
We had two copies of the Keychain class (from the time period of migrating "legacy build process" to "step-based build process" and copying stuff "not to break anything").
# How
Unified the implementations. The difference between classes was whether the class received `BuildContext` as constructor param or not.
The unified interface requires `logger` being passed in to every command (since we're using the same `Keychain` instance in multiple build phases).
# Test Plan
CI should pass.
- Rework the workflow so that the changelog is read correctly, and the changelog commit is skipped if the new entry is already present
- Split the npm check into its own release job and raise the timeout
- Serialize release runs with a concurrency group, effectively forcing them to queue
Co-authored-by: Claude Opus 5 (1M context) <[email protected]>
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
Follow-up to #4399 to upgrade typescript to latest version.
# How
Tell claude to upgrade to 6.x.
# Test Plan
CI, tests
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
This is a bit behind in typescript. 6.x is where most of our repos live.
First step is to get to highest 5.x.
# How
Tell claude to upgrade to highest 5.x.
It required a new version of `https-proxy-agent` to be compatible with new node types.
# Test Plan
`yarn start`, tests.
* [build-tools] Launch simulator packages with the resolved package manager
Serve-sim, device-hub, and Argent were hardcoded to npx or bunx. Resolve the manager the same way other steps do so EAS_FALLBACK_PACKAGE_MANAGER can switch them off the npm audit path.
* [build-tools] Override the simulator package manager instead of using the lockfile fallback
EAS_FALLBACK_PACKAGE_MANAGER only applies when no lockfile is found, so a worker yarn.lock would keep npx. EAS_OVERRIDE_PACKAGE_MANAGER wins when set. Preview still defaults to npx and Argent to bunx.
* [build-tools] Honor fallback as well as override for simulator package exec
Override still wins when set. If it is unset, EAS_FALLBACK_PACKAGE_MANAGER selects the runner so serve-sim can use bunx without a lockfile-based resolve.
* [build-tools] Add changelog for simulator package manager env
* [build-tools] Format package manager changes
* [build-tools] Honor the simulator package manager for agent-device and Appium
Install these session packages through the same env override/fallback as serve-sim, instead of hardcoding bun add --global and npm install.
* [build-tools] Sort Appium session test imports for lint
* [build-tools] Keep simulator process comments concrete
* [build-tools] Cover simulator package install and agent-device fallback
## Why
Clients are telling sandboxes through MCP server what to do. Let's handle the requests!
## How
The endeavour starts from a (relatively, after all) complex task of starting commands and reading/writing to them.
Since commands may live longer than a tool call (request followed by a response), we need some kind of manager of running commands — Shell Session Manager. (Session is the running command.)
This is where most of the complexity lays, the rest is mostly a wrapper.
## Test plan
CI should pass. Tested manually.