<!-- If this PR requires a changelog entry, add it by commenting the PR with the command `/changelog-entry [breaking-change|new-feature|bug-fix|chore] [message]`. -->
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
We're moving to Oxc in universe too. The toolset is faster than ESLint / Prettier.
# How
Asked Codex to migrate the repository. I don't think all rules got migrated, unfortunately, but also the lint are in a bit weird state (different rules in `eas-cli` vs the rest of the repo). I hope we can unify the rules soon.
# Test Plan
CI should pass.
<!-- If this PR requires a changelog entry, add it by commenting the PR with the command `/changelog-entry [breaking-change|new-feature|bug-fix|chore] [message]`. -->
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
[exponent-internal.slack.com/archives/C011ZMXQ6SZ/p1755530483378679](https://exponent-internal.slack.com/archives/C011ZMXQ6SZ/p1755530483378679)
# How
Updated GraphQL code which removed `SubmissionAndroidTrack` enum (it's a scalar now). Adjusted code to pass track around as string.
Removed `AndroidReleaseTrack` from `eas-json`. Updated `eas.schema.json` to allow any string as `track`.
Technically, to support `track: string` we'll need to update `eas-json` in `www`. I think it's ok to merge this, publish releases and then update `eas-json` in `www`. Alternatively we could publish `eas-json` from this branch as prerelease, bump in `www` and then merge this. This would be more _correct_, but I think it's ok to have this 1 hour of unannounced discrepancy between `www` and `eas-cli` (users not being able to use custom tracks _yet_).
# Test Plan
Tested along with all the pull requests in the mix.
<img width="372" height="90" alt="Zrzut ekranu 2025-09-9 o 17 03 38" src="https://github.com/user-attachments/assets/0b260ad2-2379-4597-aa1c-dae8bf86446d" />
<img width="243" height="72" alt="Zrzut ekranu 2025-09-9 o 16 59 37" src="https://github.com/user-attachments/assets/4eef353d-ac7e-4b16-9413-a304a574b685" />
<img width="449" height="110" alt="Zrzut ekranu 2025-09-9 o 17 00 40" src="https://github.com/user-attachments/assets/58a44b7a-16bb-46b4-8d98-f233c196406a" />
<img width="366" height="85" alt="Zrzut ekranu 2025-09-9 o 17 00 35" src="https://github.com/user-attachments/assets/71013cd6-5f5e-4e38-951c-008642fbee8c" />
<!-- If this PR requires a changelog entry, add it by commenting the PR with the command `/changelog-entry [breaking-change|new-feature|bug-fix|chore] [message]`. -->
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
As requested during feature review, these should live in the top-level "cli" key of eas.json.
Closes ENG-15925.
# How
Change location.
# Test Plan
`yarn tsc`
<!-- If this PR requires a changelog entry, add it by commenting the PR with the command `/changelog-entry [breaking-change|new-feature|bug-fix|chore] [message]`. -->
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
CLI change corresponding to https://github.com/expo/universe/pull/20131.
This adds the ability to override the manifest and asset hosts for EAS Update such that a set of proxy hosts can be used.
Closes ENG-15804.
# How
Considered putting these in flags, but it turned out that many many commands need to detect EAS Update configuration so they need access to these as well. Therefore, I added the new fields to `eas-json`.
The fields are:
- `manifestHostOverride` - a host to replace `u.expo.dev` in the URL.
- `assetHostOverride` - a host to replace `assets.eascdn.net` in asset URLs in the generated update manifests.
Then, in every place in EAS CLI when we generate a manifest URL, instead use the overridden URL.
Then, supply the manifest URL and asset URL overrides when creating updates (or republishes).
# Test Plan
Lengthy, but here it goes:
1. Create two proxies, one for assets and one for manifests. All these proxies do is proxy the requests.
- https://github.com/wschurman/updates-test-proxy is a proxy for the manifest request built using expo router API routes and EAS Hosting. It is hosted at https://updates-test-proxy.expo.app and just fetches the URL input but at `u.expo.dev` and returns the response.
- https://github.com/wschurman/updates-test-asset-proxy is the same but for assets. https://updates-test-asset-proxy.expo.app
2. Create an app on staging
3. Add the following to eas.json:
```
"update": {
"assetHostOverride": "updates-test-asset-proxy.expo.app",
"manifestHostOverride": "updates-test-proxy.expo.app"
}
```
4. run `neas update:configure`, see overridden URL in app.json
5. run `neas update`, see update is published, visit overridden manifest URL, see an update!
6. Visit one of the asset URLs (supplying authorization header) and see it correctly proxies.
7. configure code signing
8. publish again, see code signing works (downloads from `manifestPermalink`)
9. republish the last update, see it works and sets the overrides correctly.
<!-- If this PR requires a changelog entry, add it by commenting the PR with the command `/changelog-entry [breaking-change|new-feature|bug-fix|chore] [message]`. -->
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
Closes https://github.com/expo/eas-cli/issues/2401
# How
Add `corepack` field to `eas.json`
# Test Plan
Tests, tested manually
<!-- If this PR requires a changelog entry, add it by commenting the PR with the command `/changelog-entry [breaking-change|new-feature|bug-fix|chore] [message]`. -->
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
[ENG-14518: Add `keystoreName` field to build profile to allow selecting/creating named keystore to use for a build](https://linear.app/expo/issue/ENG-14518/add-keystorename-field-to-build-profile-to-allow-selectingcreating)
Allow specifying keystore name of credentials to be used with a build.
# How
* Added `keystoreName` to eas.json schema
* Pass `name` option to `AndroidCredentialsProvider`
# Test Plan
Added test, tested manually.
1. Create a new android credentials with `eas credentials`
2. Specify `keystoreName` in build profile in `eas.json`
3. Ensure that it works only for android builds
4. Ensure it works only for `remote` `credentialsSource`
5. Ensure that the correct credentials are used
<img width="326" alt="image" src="https://github.com/user-attachments/assets/1245c459-5fa1-4253-b5fc-bdf7a68b814a" />
<img width="628" alt="image" src="https://github.com/user-attachments/assets/5bca4cf7-c895-462c-b527-ef37ce659aca" />
* [eas-cli] don't allow to specify custom global version of deprecated `expo-cli`
* update CHANGELOG.md
* update dependencies
* print a warning vs throwing an error
* mark as deprecated
* print warning nicer
* fix changelog entry
* fix changelog
* [eas-cli] allow for `rollout` option when configuring submission
* update CHANGELOG.md
* add entry to `eas.schema.json`
* improve eas.schema.json
* make rollout default to 1 if not set
* Revert "make rollout default to 1 if not set"
This reverts commit 2ab689b02c.
* generate schema against staging
* update fragment
* [eas-cli][eas-json] add `large` resource class for iOS as allowed value in `eas.json`
* add deprecation warning for `m-large`
* add test
* update CHANGELOG.md
* [eas-cli][eas-json] handle new resource classes in EAS CLI
* show warning for large iOS resource classes
* don't deprecate resource class flag in this PR
* apply suggested improvements
* fix markdown description of top level resource class
* fix large resource class warning
* update CHANGELOG.md
* update eas.schema.json
* improve eas.schema.json
* add support for medium resource class and update eas.json
* fix error message for large resource classes
* temporary changes to solve issues with SSOUser being added to schema
* fix tests
* fix error message
* remove unnecessary dot
* update changelog
* [eas-json] Make not recognized image error handler fire only if image is present under valid key with invalid value
* revert changes to error message
* update CHANGELOG.md
* [eas-json] support `autoIncrement` at root of build profile
* [eas-json] Start `autoIncrement` markdown enum description with capital letter
* update CHANGELOG.md
* [eas-json] use interfaces instead of types
* [eas-json] fix issues with types and improve schema descriptions
* [eas-json] remove unneccessary comment
* [eas-json] make EasJsonBuildProfile interface again
* [eas-json] remove unneccessary semicolon
* [eas-json] use only boolean values for autoIncrement flag
* [eas-json] improve schema description for autoIncrement option
* [eas-json] remove change from changelog
* update CHANGELOG.md
* improve changelog entry
* [eas-cli] Add metadata context based on submission contexts
* [eas-json] Add submission meta property to config
* [eas-cli] Make exp optional in the metdata context
* [eas-cli] Fix misleading docblock on metadata context
* [eas-cli] Fix pass through exp config in metadata context
* [eas-cli] Import ios submission profile type through entrypoint
* [eas-cli] Rename metadata file to filename in context
* [eas-cli] Move credential context outside metadata context
* [eas-cli] Rename meta to metadataPath in profile config
* [eas-cli] Drop nonInteractive from metadata because of AppStoreApi limitations
* [eas-cli] Use singular store in bundle identifier doc