# Why
When publishing updates, users need to know if there are compatible builds for their fingerprints. This PR prints this information at the end of `eas update` to warn users, if they have updates being published that don't have corresponding builds, causing potential compatibility issues.
<img width="1536" alt="Screenshot 2025-04-01 at 5 09 12 PM" src="https://github.com/user-attachments/assets/400ac0d9-c39e-4aee-9793-465c6acb634e" />
# How
Added functionality to check for compatible builds when publishing updates:
1. Enhanced `fetchBuildsAsync` to support filtering by `fingerprintHash`
2. Implemented `findCompatibleBuildsAsync` to find builds matching fingerprints
3. Added warnings in the update publish command when no compatible builds are found for fingerprints
4. Included links to the fingerprint details on the Expo website for easier debugging
# Test Plan
Run `eas update` with a fingerprint that doesn't have a compatible build
# Why
This PR refactors the `UpdatePublish` command to improve code readability and flow by removing a nested `else` block and using an early return pattern.
before
```
if (jsonFlag) {
printJsonOnlyOutput(getUpdateJsonInfosForUpdates(newUpdates));
} else {
// all the logic
}
```
after
```
if (jsonFlag) {
printJsonOnlyOutput(getUpdateJsonInfosForUpdates(newUpdates));
return;
}
// all the logic
```
# How
- Removed the large `else` block that contained most of the code in the `UpdatePublish` command
- Added an early return after handling the JSON flag case
- Kept all the existing functionality intact while making the code more maintainable
- Improved the logical flow by flattening the code structure
# Test Plan
Manually tested the `eas update` command to ensure the code path works 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
I'm going to move Workflow and GitHub builds to scoped token soon. If users depend on the automatically provided `EXPO_TOKEN` _and_ the action they're going to try to do has not been whitelisted with scoped rules yet, they're going to get an `UnauthorizedError` mentioning `ScopedAccountActorViewerContext`.
On top of logs annotations (working on them [here](https://github.com/expo/universe/pull/19494)) I think we can make the error message a bit better.
# How
Special-case `ScopedAccountActorViewerContext` error in `process.env.EAS_BUILD` and print message asking the user to contact us.
Alongside this, I think https://github.com/expo/universe/pull/19500 may be a good idea.
# Test Plan
With `readRules` in `UserPrivacyPolicy` cleared out:
<img width="1440" alt="Zrzut ekranu 2025-03-31 o 23 43 00" src="https://github.com/user-attachments/assets/89245ccc-21e7-4041-98ce-21a517f932d4" />
<!-- 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
When we move Workflows to scoped token which has at most DEVELOPER permission, `type: deploy, prod: true` jobs will fail with an ominous
```
You don't have the required permissions to perform this operation.
This can sometimes happen if you are logged in as incorrect user.
Run eas whoami to check the username you are logged in as.
Run eas login to change the account.
Original error message: Entity not authorized: AppDevDomainNameEntity[00000000-0000-0000-0000-000000000000] (viewer = ScopedAccountActorViewerContext[16d62ef3-a219-47ca-936b-89958f6cb1f8], action = CREATE, ruleIndex = -1)
Request ID: 863a1317-882b-4cab-b8f2-c5f5d63b6f29
```
# How
Special-cased the `--prod` && `AppDevDomainEntity` && `CREATE` && `UNAUTHORIZED_ERROR` error.
Not sure if we should call out "as an app admin" in the error message. Open to suggestions.
# Test Plan
Ran `eas deploy --prod` as a developer-permission-only user. I've updated message in code since taking the screenshot.
<img width="836" alt="Zrzut ekranu 2025-03-28 o 21 21 02" src="https://github.com/user-attachments/assets/fc3a8b08-ae2f-4630-9e88-ccb48151d3e2" />
<!-- 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
I was thinking we can offer `EAS_NO_VCS=1` as a simple escape hatch for people that are getting weird Git-related issues. One of them may be an old version of Git that does not support our `git clone` properly.
# How
In `getRootPath` of no-VCS mode, return first of those values (in order):
- `EAS_PROJECT_ROOT`
- Git root path
- `process.cwd()`
# Test Plan
Added a basic test.
Co-authored-by: Szymon Dziedzic <[email protected]>
<!-- 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
Thanks to [a conversation on Bluesky](https://bsky.app/profile/sjchmiela.bsky.social/post/3lj6k2xo7rk2g) it turned out [this check](https://github.com/expo/eas-cli/blob/3a434940eb44dfa8dddc42af055793134ca9016f/packages/eas-cli/src/vcs/clients/git.ts#L255-L257) is invalid (always true), because `Ignore` has `DEFAULT_IGNORE`, so even if a user had no `.git` in `.easignore`, especially if they had `requireCommit: true`, `.git` would be removed.
# How
- Added a check to disallow `.easignore` if one has `requireCommit: true`.
- Changed logic around `Ignore` so we have separate `createForCopying` (ignores `.git` and `node_modules` always) and `createForChecking` (does not ignore anything by default). I don't like it, but it should work and is the best of what I could come up with without further refactoring.
# Test Plan
Added more tests.
* [eas-cli] skip creation of testflight group when there are already exisitng testflight groups + allow to opt out of the behavior by setting env var
* rename env var
* add changelog
<!-- 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
I struggled with adding a new workflow within `.eas/build` since I had `build/` in my `.gitignore`. I removed the line but it was still an issue. Turns out I had the same thing in `.easignore`. I think adding this to the error message could be helpful for others
# How
Not tested
<!-- 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
When we `git clone` the source repository and then copy worktree changes over, we add and modify files. However, we do not _delete_ files that have been deleted in worktree.
# How
When we operate in `requireCommit: false` mode, we add `--no-checkout` to the `git clone` command. This way the destination directory only has `.git` directory when we start copying files over. Thus, files deleted from worktree will not suddenly appear in tarball.
In `requireCommit: true` mode we don't add `--no-checkout`, because we don't copy files.
# Test Plan
Added test. Tested manually.
Side effect of this is that `git status` reports that all files have been deleted and there's a bunch of untracked files (which, `git add`-ed, make the repository appear as the source repo). I don't know how to copy the Git index 1-1…
<!-- 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
With `toNamespacedPath` I was finally able to make ignoring files work properly.
# How
Removed `if (__NORMALIZE)` checks.
# Test Plan
Ran `eas build:inspect` on Windows, confirmed no `node_modules` was copied. Also ran `eas build:inspect` on macOS, worked too.
<!-- 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
`fs` adds a [Win32 File Namespace](https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#win32-file-namespaces) to the beginning of the path which breaks `path.relative` if `src` does not have the namespace.
<img width="899" alt="Zrzut ekranu 2025-02-9 o 12 15 45" src="https://github.com/user-attachments/assets/942b28d1-881f-4e5d-861e-297bb5eddbf2" />
# How
Ensured that running `toNamespacedPath` on an already namespaced path does not add a _second_ namespace:
```
> path.win32.toNamespacedPath("D:\\abc")
'\\\\?\\D:\\abc'
> path.win32.toNamespacedPath(path.win32.toNamespacedPath("D:\\abc"))
'\\\\?\\D:\\abc'
```
Wrapped `src` and `srcFilePath` (two arguments to `path.relative`) with `path.toNamespacedPath` so `path.relative` works.
# Test Plan
Will release and test.
<!-- 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
Since v15 files that should be ignored get added to the tarball on Windows.
# How
After adding some debugging I was able to find that `src`, `srcFilePath` don't match on path separators which breaks `ignore.ignores`.
<img width="827" alt="Zrzut ekranu 2025-02-7 o 21 57 02" src="https://github.com/user-attachments/assets/9ed3b166-dbc0-4287-87a1-0009769e0d4d" />
Added `path.normalize` if `__NORMALIZE` is `1`.
---
Also noticed we used wrong `cwd` for is-tracked check.
# Test Plan
Going to release this and test.
<!-- 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
`requireCommit: true` setups expect worktree to be clean (e.g. encrypted files to be locked).
# How
Made it so if `requireCommit` is true we don't copy files over.
# Test Plan
I have enabled `git-crypt` in my test repository, added a secret file, ran `easd build:inspect -p android -s archive -o ~/test-production --force`. The clone did contain secret file in plaintext.
Then I enabled `requireCommit: true` and repeated the command. The clone did contain the file encrypted.
<!-- 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
`git ls-files` returns submodules as a single filepath entry, so `rm` must remove it with `-rf`. Fixes https://github.com/expo/eas-cli/issues/2883.
# How
Added `{ recursive: true, force: true }` to `fs.rm`.
# Test Plan
I tried `easd build:inspect -p android -s archive -o ~/testtest --force` on a repo with a submodule in `.easignore`. It succeeded and the submodule was not included in the folder.
<!-- 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
Adding `.git` directory to the tarball makes it bigger. Users notice this warning and want it to be actionable, but currently adding `.git` to `.easignore` does nothing.
# How
For now, raise threshold for warning from 100 MiB to 150 MiB. In the next pull request I'm going to fix `.git` exclusion via `.easignore`.
# 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
Currently it's not possible to exclude `.git` from being uploaded in project tarball.
# How
In `makeShallowCopyAsync()` we first clone the repository, then we delete files ignored by `.easignore` and then we copy working directory over.
The "delete files ignored by `.easignore`" step is governed by `git ls-files --exclude-from=.easignore`. `git ls-files` is never going to consider `.git` directory to be excluded, even if specified in `.easignore`, so we need to special-case the `.git` directory and remove it manually if specified.
# Test Plan
Added `.git` to a test `.easignore`, ran `eas build:inspect` and confirmed the copied directory did _not_ contain `.git` folder.
<!-- 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
`fs-extra` fails to copy symbolic links as one would expect. https://github.com/jprichardson/node-fs-extra/issues/708
# How
We could:
- copy and dereference symbolic links — make it so that the clone of the original directory has two copies of the files -- original and linked
- copy symbolic links without re-resolving, assuming any links will be relative and should work when unpacked on a different machine.
I think we can count on the latter.
# Test Plan
Created a link in my test repository
```
drwxr-xr-x 7 sjchmiela staff 224B Jan 28 16:14 assets
lrwxr-xr-x 1 sjchmiela staff 6B Feb 4 22:12 assets-linked -> assets
```
ran
```
easd build:inspect -p android -s archive -o ~/testtest --force
```
confirmed I see
```
drwxr-xr-x 7 sjchmiela staff 224B Feb 4 22:20 assets
lrwxr-xr-x 1 sjchmiela staff 6B Feb 4 22:20 assets-linked -> assets
```
in the result directory.
<!-- 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
`[email protected]` doesn't interpret `.easignore` right because I haven't initialized the `Ignore` class properly.
# How
Make it so it's not possible to use `Ignore` without initializing it.
# Test Plan
Tests 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
If you had an `.easignore`, `isFileIgnoredAsync` was always thinking all files are NOT ignored which was causing it to think all builds are in `.GENERIC` mode (with native code) which was not true, because ACTUALLY the files WERE ignored.
All mostly because of forgotten `ignore.initIgnoreAsync()`…
# How
Added `ignore.initIgnoreAsync()`. Also realized whether the file is tracked / not-tracked may affect how actually is it going to behave, so added it to the mix.
# Test Plan
Added tests that I think test all cases.
# Why
receiving an issue for a customer who uses eas environment and continuous-deploy-fingerprint github action. they have build variants setup in their app.config.ts. the app id, scheme and some other properties are determined by their `APP_VARIANT` variable. the `APP_VARIANT` is from eas server environment.
when continuous-deploy-fingerprint first calculates fingerprint, it uses `eas env:exec` for the `npx expo-updates fingerprint:generate` call. the `APP_VARIANT` is correctly passed.
then for `eas update` call, it doesn't pass the `APP_VARIANT` env and generates an inconsistent fingerprint.
# How
pass server env to the `getRuntimeVersionInfoObjectsAsync()` (`npx expo-updates runtimeversion:resolve`)
<!-- 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 don't need to redownload app every single time in `eas build:dev`. We can cache it locally. This functionality already exists for `eas build:run`.
# How
Use caching the same way we do for `eas build:run`
# Test Plan
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
@brentvatne suggested that it would be useful to let people know how long the previous build took when rebuilding in `eas build:dev`
# How
Get the information about how long previous build took and show it to the user
# Test Plan
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
Currently, when `eas-cli` create a project tarball for EAS Build or Workflows, unless the user has `requireCommit: true` in `eas.json`, the project is being packed with a plain `makeShallowCopyAsync` which copies all the files that are deemed ignored by `ignore` package and `.easignore` or `.gitignore` files.
This is suboptimal for `eas workflow:run` experience — a developer with a project with Git expects the repository to exist on EAS.
# How
This was a big pain.
Previously, we had `GitClient` which required commit and its subclass, `GitNoCommitClient` which overrode some functions to allow uncommitted changes. On top of that, `GitClient` copied project with `git clone`, while `GitNoCommitClient` copied it with `makeShallowCopyAsync`. This meant `GitClient`'s copy would include `.git`, whereas `GitNoCommitClient` would not. Moreover, thus, `GitClient` would adhere to `.gitignore` and `GitNoCommitClient` would _not_ — only to `.easignore`.
This pull request:
- merges the two Git clients into one with `requireCommit` option
- this causes `.git` directory to exist in copies with `requireCommit = false`
- changes how we log changes caused by Git case sensitivity change (we need to handle the case where there is a preexisting dirty tree)
- after we clone the repository, we delete files that should have been ignored according to `.easignore`
- afterwards, we make a shallow copy of all the files over to the clone. This copies live changes to the working tree over to the clean clone. (They may only exist in `requireCommit = false` situation.)
- adds better support for `.easignore` to `isFileIgnoredAsync`.
As far as I can see the behavior looks like this:

The breaking change in here is that we're going to start adhering to `.easignore` even if someone has `requireCommit = true`.
# Test Plan
I used `easd build:inspect` a bunch to verify it works like I expect. I encourage fellow reviewers to do the same.
<!-- 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
https://exponent-internal.slack.com/archives/C017N0N99RA/p1738630158821649
# How
Print warn message only once
# Test Plan
Tests
# Why
Add support for users accidentally passing in update group id into `fingerprint:compare` instead of update id.
# How
Added support for handling update group IDs in the fingerprint comparison command by:
- Attempting to fetch updates using the provided ID as an update group ID
- If successful and there's only one update, using that update directly
- If multiple updates exist in the group, prompting the user to select the specific platform/update
- Falling back to the original update ID logic if the group ID lookup fails
- Adding helpful error messages that include the direct URL to find the correct update ID
# Test Plan
- [ ] `EXPO_STAGING=1 ~/Documents/eas-cli/packages/eas-cli/bin/run fingerprint:compare --update-id ed36a46b-6cc7-4f49-88df-e6ffb66f22d2`
- [ ] `EXPO_STAGING=1 ~/Documents/eas-cli/packages/eas-cli/bin/run fingerprint:compare --update-id ed36a46b-6cc7-4f49-88df-e6ffb66f22d2 --non-interactive`
# Why
Add support for comparing fingerprints between updates using the `--update-id` flag in the `eas fingerprint compare` command. This allows developers to compare fingerprints between updates, similar to how they can already compare fingerprints between builds.
# How
- Added `updateId` flag to the `FingerprintCompare` command
- Extended the fingerprint comparison logic to handle updates as a fingerprint source
- Added `UpdateQuery.viewByUpdateAsync` to fetch update details including fingerprint information
- Updated the fingerprint origin type system to include updates as a source
- Enhanced the pretty printing of fingerprint sources to show platform information for updates
# Test Plan
- [ ] `EXPO_STAGING=1 ~/Documents/eas-cli/packages/eas-cli/bin/run fingerprint:compare --update-id 087ccb84-5b64-4285-aebf-e890cb95cd20`
* [eas-cli] add eas dev command
* update logs
* rename command do `build:dev`
* filter by dev client
* apply suggested changes
* use real vs virtaul build profiles
* make it hidden
* prompt to commit after adding new build profile
<!-- 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-14307: move environment to job object from metadata](https://linear.app/expo/issue/ENG-14307/move-environment-to-job-object-from-metadata)
`Environment` should be considering a first class citizen in job object instead of being stored in the metadata.
# How
* Pass `environment` in `job` object
* remove `environment` from `metadata`.
# Test Plan
1. Start a build specifying `environment` in `eas.json`.
2. Build should use the specified environment (check on website in `Build details`)
* Replace preview with help
* Remove redundant alias
* Update description
* Rename top level command from worker -> deploy
* Add changelog
* End sentence with a .
* Add worker:deploy as an alias to deploy
<!-- 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
Allow filtering by `--fingerprint-hash` in the `eas build:list` command
# How
Update GQL schema to add a new filter field, and add a new flag to use it.
# Test Plan
Test locally
* Allow env vars to be loaded from .env and EAS env simultaneously
* Add CHANGELOG entry
* Apply lints
* Switch to new @expo/[email protected] API
* Update packages/eas-cli/src/commands/worker/deploy.ts
Co-authored-by: Kadi Kraman <[email protected]>
---------
Co-authored-by: Kadi Kraman <[email protected]>
<!-- 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" />
<!-- 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
Thanks to @szdziedzic's changes to `www`, if we send a `package.json` along with `eas.json` when setting up a workflow run, EAS will pick the right images based on SDK and RN versions as `eas build` would.
# How
Added uploading `package.json` after uploading `eas.json`, added the new argument to the mutation.
# Test Plan
Tested manually.
<img width="874" alt="Zrzut ekranu 2024-12-20 o 22 27 20" src="https://github.com/user-attachments/assets/383c4a19-17a1-4f46-8113-bc6dc8aaba2e" />
<img width="833" alt="Zrzut ekranu 2024-12-20 o 22 27 58" src="https://github.com/user-attachments/assets/be9e2396-0779-4043-925f-d784b5168764" />
<!-- 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-14328: store `environment` info on update entity](https://linear.app/expo/issue/ENG-14328/store-environment-info-on-update-entity)
Pass `environment` to `PublishMutation.publishUpdateGroupAsync` to store in the db.
Waits for changes on the `www`. https://github.com/expo/universe/pull/17921
<!-- 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
It seems like this file includes redundant entries + is not up to date
# How
Remove redundant entries, add @radoslawkrzemien to global codeowners, make @wschurman and @quinlanj codeowners of everything EAS Update related (including channel commands), remove @byCedric and @EvanBacon from EAS Update codeowners
# Test Plan
Review
<!-- 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
https://discord.com/channels/695411232856997968/1309202098591633458/1311040361040183429
# How
Make warning up to date after recent env vars changes
# Why
Update `@expo` packages to SDK 52 versions
# How
Update `@expo` packages to SDK 52 versions
Fixes#2696
It seems like the `privacy` field was removed from the expo config in the SDK 52 update: https://expo.dev/changelog/2024/11-12-sdk-52.
I used `AppPrivay.Unlisted` for the `createApp` mutation input for which this is still required. It was an option selected for an app when `exp.privacy` was undefined.
It also seems that `findWorkspaceRoot` function in `@expo/package-manager` was changed to `resolveWorkspaceRoot`.
# Test Plan
Tests, test commands 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
https://exponent-internal.slack.com/archives/C06FK950085/p1732258126230829
# How
Improve logs
# Test Plan
Tests
<!-- 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
Add environment to `eas.schema.json`
# How
Add environment to `eas.schema.json`
<!-- 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
https://exponent-internal.slack.com/archives/C06FK950085/p1729212611408479?thread_ts=1729186741.835629&cid=C06FK950085
# How
Resolve the default (if not set in the build profile) `environment` to use for a build based on its configuration.
Store build -> `production`
Dev client -> `development`
Other (`internal`) -> `preview`
# Test Plan
Test 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
Make `eas env` commands visible
# How
Make `eas env` commands visible
# Test Plan
Tests
<!-- 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
Deprecate old secret commands
# How
Mark as hidden + print warn when used
# Test Plan
Tests
# Why
This PR computes a fingerprint for each update.
- If the update does not use the fingerprint policy, it calculates the fingerprint using the exported cli in the `expo` package for projects SDK 52+.
- If the update uses the fingerprint policy, it just uses the fingerprint that was previously calculated using `expo-updates`.
# How
- Modified fingerprint computation to handle platform-specific cases
- Updated the fingerprint data structure to use `fingerprintHash` instead of the full fingerprint object
- Added support for computing fingerprints for projects without expo-updates
- Introduced new types and interfaces for handling fingerprint information groups
- Created utility functions for async map operations and fingerprint calculations
- Updated GraphQL schema to support new fingerprint-related fields
# Test Plan
- [x] on build: verify fingerprints till work
- [x] on update: verify fingerprint is calculated for new project with SDK 52
- [x] on update: verify no fingerprint is calculated for old project (< SDK 52)
- [x] on update: verify fingerprint is reused for project with fingerprint runtime policy
<!-- 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
Make class names more consistent with other commands
Improve descriptions
# How
Make class names more consistent with other commands
Improve descriptions
# Test Plan
Tests
<!-- 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
Stick to account-wide everywhere for now
# How
Rename shared to account-wide, fix some bugs and type issues
# Test Plan
Tests
# Why
Adds `eas workflow:create` to make it faster to create workflow files in a project. This command creates a file like **.eas/workflows/workflow.yml**. The user can choose the file name or can provide it as an arugment.
# Screenshots
<img width="552" alt="Screenshot 2024-11-08 at 8 50 58 AM" src="https://github.com/user-attachments/assets/5cf82e7e-cce6-4098-b291-fccdac25f103">
<img width="584" alt="Screenshot 2024-11-08 at 8 51 27 AM" src="https://github.com/user-attachments/assets/d6f6e7cb-18c1-420e-b52a-5bdd42446715">
<img width="617" alt="Screenshot 2024-11-08 at 8 52 04 AM" src="https://github.com/user-attachments/assets/81cc79cf-afb7-4855-bfce-0679f98655fa">
# Test Plan
Make sure that you can run the command as pictured above and that it correctly creates the workflow file. Also make sure that the unit tests pass.
# Future
Once we have docs for workflows that are public, I'd like to put a link to the docs in the default file this command creates. For now, I am just putting Hello World as a reasonable placeholder.
Co-authored-by: Szymon Dziedzic <[email protected]>
Co-authored-by: Stanisław Chmiela <[email protected]>
<!-- 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
Going to release soon.
# How
Removed `hidden = true` overrides.
# Test Plan
`easd --help` printed out information about workflow commands.
```
~/Developer/test-local (main [$!]) easd --help
EAS command line tool
VERSION
eas-cli/13.1.1 darwin-arm64 node-v22.4.0
USAGE
$ eas [COMMAND]
TOPICS
...
workflow manage workflows
```
```
~/Developer/test-local (main [$!]) easd workflow --help
manage workflows
USAGE
$ eas workflow:COMMAND
COMMANDS
workflow:run Run an EAS workflow
workflow:validate validate a workflow configuration yaml file
```
<!-- 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
- running workflows requires GitHub connection
- workflow config may be a valid YAML, but invalid config
We want to check both of these:
- in `workflow:validate`
- before we upload project sources to GCS in `workflow:run`.
# How
I added a `validateWorkflowRevisionYamlConfig` mutation I'm using here to validate the config _and_ GitHub connection. The GitHub requirement is checked dynamically in `www` so we can later remove it without having users upgrade to a newer `eas-cli`.
Brent also wished `eas workflow:run test.yml` resolved `test.yml` to `.eas/workflows/test.yml` automatically, so added this too.
# Test Plan
I tried validating and running invalid YAMLs, workflows and valid configs. Things seemed to work ok.
<!-- 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
During dogfooding it came out that this flag is too long and confusing
# How
Just use `environment`
# Test Plan
Tests, types
<!-- 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
Counterpart of https://github.com/expo/eas-cli/pull/2677, applied to `submit:internal`.
# How
Copied the solution from `build:internal`.
# Test Plan
None.
<!-- 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 need to use `build:internal` to resolve build configuration in GCS workflow jobs which have no Git repository.
# How
I'm going to be adding `EAS_NO_VCS=1` to GCS workflow jobs. This should prevent `build:internal` from requiring Git repository.
# Test Plan
I have verified `EAS_BUILD_ID=d7fb9f5c-dce0-40e2-b459-cbc05ba1ed77 EAS_NO_VCS=1 easd build:internal -p android` prints the JSON output on my computer.
<!-- 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 want to allow users to start workflows manually.
# How
I added a `createRunMutation` to GraphQL and used it here. We upload project archive, `eas.json` and use to start a new workflow run.
# Test Plan
```
Workflows are in beta and subject to breaking changes.
Compressing project files and uploading to EAS. Learn more: https://expo.fyi/eas-build-archive
✔ Uploaded eas.json to EAS
✔ Uploaded project archive to EAS 1s
✔ Workflow started successfully. https://staging.expo.dev/accounts/sjchmiela/projects/staging-app/workflows/019301f1-b1b4-700d-9e3b-82dc97d76a32
```
Co-authored-by: Szymon Dziedzic <[email protected]>
<!-- 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
update expo packages to SDK 51 versions
revert https://github.com/expo/eas-cli/pull/2524
# How
update expo packages to SDK 51 versions
# Test Plan
tests
<!-- 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
https://exponent-internal.slack.com/archives/C02123T524U/p1724970663050089?thread_ts=1724924614.773089&cid=C02123T524Uhttps://exponent-internal.slack.com/archives/C5ERY0TAR/p1725002816077089
Generally `@expo/config`, `@expo/prebuild-config`, and `@expo/config-plugins` are per SDK concept. Currently, in EAS CLI, we rely on one version of the `@expo/...` package to work well globally for all SDKs. It seems to sometimes bite us like in the case of https://exponent-internal.slack.com/archives/C02123T524U/p1724909908574979, because SDK 51 config wasn't compatible with SDK 50.
It's better to switch to using config-related functions shipped with `@expo/config`, `@expo/prebuild-config`, and `@expo/config-plugins`. I believe we can assume that `getConfig`, `getPrebuildConfig`, and `compileModsAsync` shipped with these packages have stable API https://exponent-internal.slack.com/archives/C5ERY0TAR/p1725293002128849?thread_ts=1725002816.077089&cid=C5ERY0TAR.
# How
Use `getConfig`, `getPrebuildConfig`, and `compileModsAsync` from `@expo/config`, `@expo/prebuild-config`, and `@expo/config-plugins` shipped with Expo SDK installed in the user's project. If not available, fallback to versions installed per SDK. If we can assume that these guarantee stable API we can use types of these functions from packages installed for EAS CLI as well.
# Test Plan
Run builds for repro case of https://exponent-internal.slack.com/archives/C02123T524U/p1724909908574979 with SDK 51 config packages installed for EAS CLI (that previously broke it), see that it works and capabilities are correctly synced.
Initiate a new bare RN project using community CLI, and check that it works as well using fallback config loading.
<!-- 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
Add support for `with-eas-environment-variables-set` flag in `eas update:configure` command
# How
Use the flag the same way we do for `eas update`.
# Test Plan
Run command.
<!-- 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
Make the `with-eas-environment-variables-set` flag reusable and improve type safety and description.
# How
Extract `with-eas-environment-variables-set` to separate file. Improve validation and type safety.
# Test Plan
Run command locally.
<!-- 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
Add new Xcode 16.1 image and `sdk-52` tag to `eas.schema.json`
# How
Add new Xcode 16.1 image and `sdk-52` tag to `eas.schema.json`
# Test Plan
Tests
# Why
[ENG-13930: Allow passing environment without the flag](https://linear.app/expo/issue/ENG-13930/allow-passing-environment-without-the-flag)
Added capability to pass `environment` without `--environment` flag to `eas env:*` commands. This is often more intuitive.
This works only for a single environments. In case user wants to pass more than one, `--environment` flag should still be used.
# Changed commands
## `env:create`
* was only `env:create --name thisisvar --value thisinew --visibility plaintext --environment production`
* now also `env:create production --name thisisvar --value thisinew --visibility plaintext`
## `env:delete`
* was only `env:delete --variable-environment production --variable-name NEW_VAR`
* now also `env:delete production --variable-name NEW_VAR`
## `env:exec`
* was only `env:exec --environment development 'echo lol'`
* now also `eas env:exec development 'echo lol'`
## `env:get`
* was only `env:get --variable-environment development --variable-name HELLO`
* now also `env:get development --variable-name HELLO`
## `eas env:link`
* was only `eas env:link --environment preview --variable-name NAME`
* now also `eas env:link preview --variable-name NAME`
## `eas env:list`
* was only `eas env:list --environment preview`
* now also `eas env:list preview`
## `eas env:pull`
* was only `eas env:pull --environment production`
* now also `eas env:pull production`
## `eas env:push`
* was only `eas env:push --environment production`
* now also `eas env:push production`
## `eas env:unlink`
* was only `eas env:unlink --environment production --variable-name NAME`
* now also `eas env:unlink production --variable-name NAME`
## `eas env:update`
* was only `eas env:update --variable-environment production --variable-name HELLO --environment development`
* now also `eas env:update production --variable-name HELLO --environment production`
# Test Plan
Updated tests
<!-- 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 suggested in the base PR we need a simple context focused on only getting the project ID, without specifying the server-side environment and resolving Expo config with it.
# How
Add such context. Make the `withServerSideEnvironment` argument required for standard project config context.
# Test Plan
Tests, test 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
https://exponent-internal.slack.com/archives/C013ZK4SA12/p1725644220583309
We are planning to introduce enhancements to our env vars system soon. Currently, we only allow people to keep secrets on EAS servers. Secrets are not readable outside of EAS servers so of course EAS Update doesn't work with them. In a new system, people can also store readable env vars on our servers, which opens new possibilities about how EAS Update can interact with env vars!
In this PR I'm adding support for the `--with-eas-environment-variables-set production|preview|development` flag. If used, we use the flag's value to fetch readable env vars from our servers and use it in the `expo export` command to produce an update bundle based on these env vars. If the flag is used I'm using the `EXPO_NO_DOTENV` flag to disable Expo CLI from loading env vars from `.env` files and potentially unwillingly overwriting env vars fetched from our servers for a given environment.
Users seem to face big issues with using env vars with EAS Build & Update at the moment, originating from the fact that these 2 handle different, non-compatible ways of using env vars. Env vars in the build profile and server-side secrets vs local env vars + `.env`. With this flag it will be easy to avoid envs mismatch by doing `eas update ----with-eas-environment-variables-set environment` and `eas build` with `{ ..., environment: environment, ...} in the build profile!
# How
Add a new hidden (for now) flag `--with-eas-environment-variables-set` that indicates which environment to use. If used fetch env vars from server. Merge and overwrite `process.env` with newly fetched env vars. Use them to resolve the expo config. Don't use `.env` env var loading from Expo CLI if server-side env vars are used.
# Test Plan
Test manually. Run `eas update` with and without a new flag. Check that the expo config is resolved correctly.
# Why
File variables were not handled by the `env:pull` command. They should be downloaded just like the other values.
# How
* `env:pull` saves file type variables to `.eas/.env` directory and sets its value in `.env.local` file to its file path
* `env:push` skips file type variables
# Test Plan
Tested manually
# Why
We want to allow developers to prevent updates from being served to certain builds by "pausing" update channels.
# How
- I added two new CLI commands to toggle the channel pausing state
- I added the pause status to the channel details output in the `view` and `list` commands
# Test Plan
Build the CLI locally under the `neas` alias, and run `neas channel:pause development && neas channel:view development && neas channel:resume development && neas channel:view development`:
<img width="1364" alt="Screenshot 2024-10-17 at 05 33 36" src="https://github.com/user-attachments/assets/fd557e57-bbf7-463c-8cec-1febcb2fdde8">
# Why
[ENG-13853: Prompt user to enter the environment when not provided vs fail and rerun when using `eas env:push`](https://linear.app/expo/issue/ENG-13853/prompt-user-to-enter-the-environment-when-not-provided-vs-fail-and)
If the environment is not provided, we ask the user about it in other commands, I think we can do the same here for consistency vs throwing an error and having the user rerun it
# Test Plan
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
Rely on ExpoConfig type from the `@expo/config` package in all places for consistency
# How
Rely on ExpoConfig type from the `@expo/config` package in all places for consistency
# Test Plan
Tests
# Why
User should be able to upload files to environment variables and read content of those files
# How
* When an envvar is created with flag `--type FILE`, selected file is encoded to base64 and sent to www.
* EnvVarQueries return file contents when `includeFileContent` file is passed
* `env:get` automatically include file content, `env:list` requires `--include-file-content` flag
* Updated environment display - added `environments`, `type` and `visibility`
# Test Plan
tested manually, updated tests
<!-- 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-13525: Update EAS-CLI for new EnvVar features](https://linear.app/expo/issue/ENG-13525/update-eas-cli-for-new-envvar-features)
Update command to use multiple environments, polish the interface.
# How
* use `variable-name` and `variable-environment` to select the variable
* Use `multiselect` and multiple `environment` parameters to allow unlinking multiple envs
All commands that were using name parameter to identify a single variable will use variable-name and variable-environment instead. This change will enable user to distinguish between name and environment that is identifying variable that is acted upon, and name and environment that is a parameter for command.
For example, when the user wants to update variable TEST that has environment production and change its name and change its environment, they can use:
eas env:update --variable-name TEST --variable-environment production --name TEST-update --environment production --environment preview
# Test Plan
Added tests
<!-- 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-13525: Update EAS-CLI for new EnvVar features](https://linear.app/expo/issue/ENG-13525/update-eas-cli-for-new-envvar-features)
Allow selecting multiple environments to display variables from.
# How
* Use `multiselect`, allow specifying multiple `environment` parameters
* List variables from all environments
# Test Plan
Added tests
<!-- 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-13525: Update EAS-CLI for new EnvVar features](https://linear.app/expo/issue/ENG-13525/update-eas-cli-for-new-envvar-features)
Add tests, polish the interface
# How
* Use `variable-name` and `variable-environment` to select the variable
* More robust selector of variable to remove ambiguity
* Use multiselect to clearly indicate which environments are linked and which are not
* Automatic `link` and `unlink` action
All commands that were using name parameter to identify a single variable will use variable-name and variable-environment instead. This change will enable user to distinguish between name and environment that is identifying variable that is acted upon, and name and environment that is a parameter for command.
For example, when the user wants to update variable TEST that has environment production and change its name and change its environment, they can use:
eas env:update --variable-name TEST --variable-environment production --name TEST-update --environment production --environment preview
# Test Plan
Added tests
<!-- 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-13525: Update EAS-CLI for new EnvVar features](https://linear.app/expo/issue/ENG-13525/update-eas-cli-for-new-envvar-features)
Rework the EnvironmentVariableUpdate function - user is able to alter name, and environments.
# How
* Added `--variable-name` and `--variable-environment` parameters to identify the variable to update
* Using parameters from `--name` and `--environment` to update the variable using the new `updateEnvironmentVariable` method.
All commands that were using name parameter to identify a single variable will use variable-name and variable-environment instead. This change will enable user to distinguish between name and environment that is identifying variable that is acted upon, and name and environment that is a parameter for command.
For example, when the user wants to update variable TEST that has environment production and change its name and change its environment, they can use:
eas env:update --variable-name TEST --variable-environment production --name TEST-update --environment production --environment preview
# Test Plan
Added tests
<!-- 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-13525: Update EAS-CLI for new EnvVar features](https://linear.app/expo/issue/ENG-13525/update-eas-cli-for-new-envvar-features)
Improve the selector for the variable to delete, rename parameter `name` to `variable-name`.
All commands that were using name parameter to identify a single variable will use variable-name and variable-environment instead. This change will enable user to distinguish between name and environment that is identifying variable that is acted upon, and name and environment that is a parameter for command.
For example, when the user wants to update variable TEST that has environment production and change its name and change its environment, they can use:
eas env:update --variable-name TEST --variable-environment production --name TEST-update --environment production --environment preview

# Test Plan
Added tests
<!-- 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-13525: Update EAS-CLI for new EnvVar features](https://linear.app/expo/issue/ENG-13525/update-eas-cli-for-new-envvar-features)
Polished the interface:
- user is prompted for environment only when the name is ambiguous.
- changed `name` parameter to `variable-name`.
All commands that were using `name` parameter to identify a single variable will use `variable-name` and `variable-environment` instead. This change will enable user to distinguish between `name` and `environment` that is identifying variable that is acted upon, and `name` and `environment` that is a parameter for command.
For example, when the user wants to update variable `TEST` that has environment `production` and change its name and change its environment, they can use:
`eas env:update --variable-name TEST --variable-environment production --name TEST-update --environment production --environment preview`
# Test Plan
Added tests
<!-- 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-13525: Update EAS-CLI for new EnvVar features](https://linear.app/expo/issue/ENG-13525/update-eas-cli-for-new-envvar-features)
Update `eas env:create` to accept multiple `--environment` parameters.
# How
* Use `EASMultiEnvironmentFlag` in `EnvironmentVariableCreate`
* Update variable display with `environment` and `updatedAt` fields
# Test Plan
Added tests
<!-- 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-13525: Update EAS-CLI for new EnvVar features](https://linear.app/expo/issue/ENG-13525/update-eas-cli-for-new-envvar-features)
EnvVar will support having multiple environments, CLI should support this.
# How
* Add an optional parameter `multiple` to `promptVariableEnvironmentAsync`
* Update commands using `promptVariableEnvironmentAsync`
* Add a new flag `EASMultiEnvironmentFlag`
# Test Plan
Tested manually, tests will be added in the following PRs
<!-- 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-13525 Update EAS-CLI for new EnvVar features](https://linear.app/expo/issue/ENG-13525/update-eas-cli-for-new-envvar-features)
Bring up to date `create` and `update` EnvVar mutations.
# How
* Use `updateEnvironmentVariable` operation instead of `createEnvironmentVariable` with an 'overwrite' option.
* Add `type` parameter
* Add `environment` parameter for shared variables
# Test Plan
Tested manually, tests will be added in the following PRs
<!-- 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-13525 Update EAS-CLI for new EnvVar features
](https://linear.app/expo/issue/ENG-13525/update-eas-cli-for-new-envvar-features)
Update EnvVar queries - allow quering using environments.
# How
* Added optional `environment` parameter to queries
* Fix typing of the `--environment` parameter
# Test Plan
Tested manually
* Update API functions for new upload endpoint and deploy result
* Fix listWorkerFilesAsync file type
* Add call to finalize deployment
* Update CHANGELOG
* Add retries to /deploy/finalize call
* Apply lints
<!-- 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
https://exponent-internal.slack.com/archives/C017N0N99RA/p1726226230206999
Right now the only way to exit the `eas credentials` command is to kill the process by doing ctrl+c. Let's add an `exit` option to the interactive menu.
# How
Add exit option to menu.
# Test Plan
Test 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
On Friday's meeting, we agreed that having both a flag and a field in the build profile for setting the environment might be too much. Additionally, we already have a `--profile` flag that has a `-e` alias which makes it even more confusing. We decided to delete the flag to avoid confusion and make it as straightforward as possible.
# How
Delete the `--environment` flag for build-related commands, rely only on the `environment` field in eas.json.
# Test Plan
Tests
<!-- 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
Add the `eas env:exec` command. This command allows you to run any arbitrary bash command with env vars from a given environment.
# How
Add `eas env:exec` command
# Test Plan
Test manually

* refactor(eas-cli): split prompt from dev domain assignment and support it non-interactive
* docs: add changelog entry
* docs: fix changelog entry
* fix(eas-cli): use proper name in "already taken" prompt
* chore: resolve linting issue
# Why
Almost a year ago we've migrated from using a single file for submission logs to multi-file logs, accommodating need to display logs from both the worker and the scheduler that is starting the worker VM.
Companion to https://github.com/expo/universe/pull/16873.
# How
Replaced `logsUrl` with `logFiles`, adjusted code.
# Test Plan
Logs printed
<img width="1055" alt="Zrzut ekranu 2024-09-24 o 23 06 22" src="https://github.com/user-attachments/assets/6c9a45c0-6760-4629-82e3-a79d5ef99ebe">
<!-- 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
I want to add support for submissions as part of workflows, where, when we start the job, we don't have access to the repository. So, we need to resolve submission config _somewhere_, ideally where we are isolated, can easily clone project, install dependencies and resolve dynamic config.
As we do with `eas build:internal`, I expect it will make sense to do `eas submit:internal` which will do what `eas submit` does usually — resolve all the credentials, using local filesystem or Expo servers and then fetch the _actual_ keys from Expo servers.
# How
First, I changed structure of `SubmitCommand`/`Submitter` a bit — previously, `SubmitCommand` would create the `Submitter` and call `submitAsync` _inside_ `runAsync()`. After my changes `SubmitCommand` will create _and return_ the `Submitter` and the call site will need to call `submitAsync`.
By doing it this way I was able to add a `getSubmissionInputAsync` to `BaseSubmitter` which returns all-resolved submission input, as-it-would-have-been-used-in-submission-mutation. This ensures the same behavior for `eas submit` and `eas submit:internal`.
Once we have that, `eas submit:internal` is relatively straightforward:
1. create `SubmitCommand`, get `Submitter`.
2. `getSubmissionInputAsync`.
3. fetch necessary credentials by IDs from `www` (https://github.com/expo/universe/pull/16793).
4. validate that we have it all (https://github.com/expo/eas-build/pull/443) and print the JSON.
# Test Plan
I was able to run `easd submit:internal` locally and got the JSON output.
<!-- 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
In a submit job we're going to have an IPA/APK to submit. We don't want to resolve any bundle identifiers from the project, we can use one from that IPA/APK.
# How
Let the override env variable override bundle identifier resolution if the workflow is managed too.
# Test Plan
I used it to submit an IPA with workflows.
* refactor(eas-cli): enhance the `--environment` help description
* docs(eas-cli): add changelog entry
* docs(eas-cli): add missing periods to `eas worker:alias --help`
* refactor(eas-cli): enhance the `--environment` help description
* fix(eas-cli): hide project export date when not older than 1m
* fix(eas-cli): add back no export error
* docs(eas-cli): add changelog entry
* chore(eas-cli): add `--platform=web` to error command
* docs(eas-cli): fix changelog entry
* refactor(eas-cli): always default to static uploads and add modified time
* docs(eas-cli): add changelog entry
* chore(eas-cli): resolve linting issue
* fix(eas-cli): error when there are no deployments
* fix(eas-cli): remove unused `exp` var
* fix(eas-cli): fix json output again
* feature(eas-cli): add `worker:alias --prod` flag to promote existing deployments
This also includes some clean ups and log utility sharing
* feature(eas-cli): support `worker:promote --prod --id`
* refactor(eas-cli): rename `/serverless/deployments` -> `/hosting/deployments`
* docs(eas-cli): add changelog entry
* chore(eas-cli): resolve linting issues
* fix(eas-cli): disable ora when possibly asking for a dev domain
* chore(eas-cli): resolve typing issue
* feature(eas-cli): add `worker --export-dir` flag to select export folder
* docs(eas-cli): add changelog entry
* fix(eas-cli): use `path.join` instead of `path.resolve`
`path.resolve` throws when the path does not exist, `path.join` uses our own validation errors.
* docs(eas-cli): fix changelog entry
* refactor(eas-cli): reuse same working in `eas worker:alis` from `eas worker`
* refactor(eas-cli): reuse same result table from `eas worker`
* docs(eas-cli): update changelog entry
* refactor(eas-cli): use `Alias URL` instead of `Aliased URL`
* refactor(eas-cli): add support for both `--prod` and `--production` flags in `eas worker`
* chore: add changelog entry
* refactor(eas-cli): also tweak `--help` output
* refactor(eas-cli): move `--prod` before `--alias`/`--id` in usage
* refactor(eas-cli): clean up ora spinners and add table output
* refactor(eas-cli): simplify project type detection
* refactor(eas-cli): simplify alias and production spinners
* docs(eas-cli): update changelog entry
* chore: resolve linting issues
* refactor(eas-cli): use `Alias URL` instead of `Aliased URL`
* fix(eas-cli): mark `production` as bold in ora spinners
* fix(eas-cli): avoid adding `expo.extra` data from config plugins in `eas init`
Note that in the newer `@expo/config` package, modifying now also merges existing properties. Once thats released, we can use that instead of manually merging this data.
* docs(eas-cli): add changelog entry
* feature(eas-cli): add `worker:alias` command to assign aliases
* feature(eas-cli): add worker selection when assigning alias
* refactor(eas-cli): clean up comments and prompt for alias
* refactor(eas-cli): clean up command and flag descriptions
* chore: resolve linting issues
* docs: add changelog entry
* Add `@expo/env`
* Source env variables from ".env" via `@expo/env` to deployment
* Add CHANGELOG
* Increase requested range for `@expo/env`
* Apply lints
* Added --non-interactive and --force support when --id is not passed to eas init command
* Removed id dependency from init command flags
* Bump undici from 5.19.1 to 5.26.3
Bumps [undici](https://github.com/nodejs/undici) from 5.19.1 to 5.26.3.
- [Release notes](https://github.com/nodejs/undici/releases)
- [Commits](https://github.com/nodejs/undici/compare/v5.19.1...v5.26.3)
---
updated-dependencies:
- dependency-name: undici
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <[email protected]>
* Revert "Bump undici from 5.19.1 to 5.26.3"
* Apply suggestions from code review
Co-authored-by: Szymon Dziedzic <[email protected]>
* Fixed initializeWithoutExplicitIDAsync not being used
* Require force flag to use default account when no account name is specified in non-interactive mode
* Changed error message when user has access to multiple accounts in non-interactive mode
* Added changelog entry
* Update CHANGELOG.md
Co-authored-by: Szymon Dziedzic <[email protected]>
---------
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Ryan Button <[email protected]>
Co-authored-by: Szymon Dziedzic <[email protected]>
* [fix]: correctly retrieve entitlements for extensions using their own target name
Fixed an issue where extensions were incorrectly retrieving the main app's entitlements instead of their own. Updated the code to use `dependency.name` for fetching the correct entitlements.
* update CHANGELOG.md
---------
Co-authored-by: Harris Han <[email protected]>
<!-- 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
companion to https://github.com/expo/third-party/pull/104
# How
This is my first PR adding new capabilities so please double-check if I did everything correctly, I based it on 6389f52
I got new entitlements from https://developer.apple.com/documentation/bundleresources/entitlements?changes=latest_major and added all available capabilities corresponding to these.
# Test Plan
Run prod build manually, add new entitlements for new capabilities to app config, and verify that they were enabled on the provisioning profile
<!-- 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
https://exponent-internal.slack.com/archives/C02123T524U/p1724909908574979
It seems like SDK 51 config-related packages update broke builds for older SDKs
# How
I believe we didn't add any new config-related features in SDK 51, so resolving the config using the package version for SDK 50 should be ok for now and shouldn't cause any trouble.
Revert #2498
# Test Plan
Tests
<!-- 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
https://github.com/expo/eas-cli/issues/2519
I was able to reproduce the issue and it is indeed true. It seems like we mistakenly added a static project config definition to the `eas build` command context in https://github.com/expo/eas-cli/commit/56510f092527e458aa9dca19feac0b5d425dac56#diff-cd2e00f4d286a4714f8736e14c635f4c3b98c402367cd71a83e4cd743034bd79. The output from it wasn't really used anywhere, but adding it caused the app configs to be evaluated without `buildProfile.env` in the first pass when trying the resolve project ID and slug at the begging of command execution and our slug/project ID assertions to fail. It only affected people with dynamic project IDs and slug fields.
# How
Remove unnecessary static context from context definitions, therefore avoid resolving project ID and slug from app config without env vars as a first thing when the `eas build` command is executed.
# Test Plan
Tested manually
* Add fingerprint sources to build metadata
* Upload fingerprint to google cloud
* Rename fingerprintGCSLocation -> fingerprintGCSBucketKey
* Add fingerprint source in an object
* Update dependencies
* Add comment about fingerprintSources
* Add a changelog entry
* Add support for local build plugin
* Add safety check that a temp directory exists
* [eas-cli] make sure we filter out any comments in `build.gradle` file before passing to to `gradle-to-js` parser
* use trim
* add test
* add changelog
* chore: update node versions to test with to 18, 20, 22
* update CHANGELOG.md
* chore(eas-cli)!: bump minimum supported Node version to 18
This makes the PR a breaking change.
* docs(eas-cli): add breaking change(log) entry
* chore: update `engines.node` to 18 everywhere
<!-- 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 want to save the relationship between a job run and an update.
# How
See https://github.com/expo/universe/pull/15329.
# Test Plan
Tested with staging.
<!-- 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
I noticed logs look off in CI when running `eas update --auto`.
<img width="1000" alt="Zrzut ekranu 2024-05-10 o 17 50 10" src="https://github.com/expo/eas-cli/assets/1151041/ed50d014-62f1-4342-bde2-0673f49d52b4">
# How
I pinpointed it to Ora being restarted on every log.
# Test Plan
Ran `CI=1 easd update --auto` and got ⬇️ which I think is much more readable.
```
CI=1 easd update --auto
- Exporting...
[expo-cli] Starting Metro Bundler
[expo-cli] Android Bundling complete 3492ms
[expo-cli] iOS Bundling complete 3493ms
[expo-cli] iOS Building Hermes bytecode for the bundle
[expo-cli] Android Building Hermes bytecode for the bundle
[expo-cli]
[expo-cli] Bundle Size
[expo-cli] ┌ index.ios.hbc 858 kB
[expo-cli] ├ index.android.hbc 864 kB
[expo-cli] ├ index.ios.hbc.map 3.45 MB
[expo-cli] └ index.android.hbc.map 3.48 MB
[expo-cli]
[expo-cli] 💡 JavaScript bundle sizes affect startup time. Learn more: https://expo.fyi/javascript-bundle-sizes
[expo-cli] Finished saving JS Bundles
[expo-cli] Dumping asset map
[expo-cli] Dumping source maps
[expo-cli] Preparing additional debugging files
[expo-cli] Export was successful. Your exported files can be found in dist
✔ Exported bundle(s)
- Uploading...
✔ Uploaded 2 app bundles
✔ Uploading assets skipped - no new assets found
ℹ 1 iOS asset, 1 Android asset (maximum: 20000 total per update). Learn more about asset limits: https://expo.fyi/eas-update-asset-limits
- Publishing...
✔ Published!
```
<!-- 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
Implementing @tchayen's suggestion.
# How
Changed wording
# Test Plan
None.
* [eas-cli] add eas onboarding flow
* mark command as hidden and prompt user before starting any action
* add gql queries
* regenerate gql schema
* fix type issues
* mark isCLIDone as true
* apply suggested changes
* improvements after cr
* more improvements
* [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] don't prompt to set up push notifications if `promptToConfigurePushNotifications` is `undefined` and `expo-notifications` is not present
* update eas.schema.json
* update CHANGELOG.md
* [eas-cli] improve error message displayed when EAS CLI version doesn't satisfy minimal version required specified in `eas.json`
* fix typo
* update CHANGELOG.md
* [eas-cli] don't prompt user to set `android.package` and `ios.bundleIdentifier` value when runing in non-interactive mode
* update CHANGELOG.md
* rename test
* [ci] bump `@expo/eas-json` version in universe after the release
* Update .github/workflows/release.yml
* test
* edit eas.json
* Revert "edit eas.json"
This reverts commit 3979a1b1fb.
* Revert "test"
This reverts commit 69db39f548.
* [eas-cli] mark `default` image tag as deprecated
* add new image tags to `eas.schema.json`
* update CHANGELOG.md
* update CHANGELOG.md
* deprecate JDK 8 and NDK r19c images
* update CHANGELOG.md
* use better warn message for Xcode < 14 images and link to our changelog post
* update warn message
* don't deprecate Androdi images in this PR
* fix changelog
* use correct latest image
* [eas-cli] create new `init-build` command under the `credentials` topic
* get hacky version of cli command working
* add all option to flag
* extend the Manage<Platform> actions to reduce code duplication
* prompt user for platform if it doesn't exist
* prompt the user to choose a profile
* add a changelog entry
* call SetUpBuildCredentials for android
* [eas-cli] bump `@expo/apple-utils` to switch between `developer.apple.com` and `developer-mdn.apple.com` domains when one of them is not working
* update CHANGELOG.md
* bump version
* [eas-cli] send a path to custom build config to EAS Build server with posix separator for Windows
* add process.platform to if statement
* update CHANGELOG.md
* apply suggestions from cr
* remove unnecessary check
* apply suggested change
# Why
We want users to feel like they're adding something we support.
# How
Added `config` property to build profile level and platform-specific profile properties levels.
Also prettified the file according to my JSON Tools VS Code extension. Let me know if it should be deprettified.
# Test Plan
None.
* [fcmv1] Manage FCM V1 Google Service Account Key in CLI
# Why
NOTE: DO NOT LAND THIS UNTIL GRAPHQL CHANGES LAND IN WWW
We're adding support for FCM V1 credentials, as Google is shutting down
the FCM Legacy API for sending Android notifications in June.
# How
Add new prompts and refactor existing prompts to match this schematic:
# Test Plan
Verified all functionality e2e:
* update CHANGELOG.md
<!-- 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
It is currently not possible to use `if: ${ always() }` in Custom Build workflows due to outdated `@expo/steps` dependency.
# How
Added a GitHub workflow, similar to the one we have in `turtle-v2`, which will automatically upgrade all dependencies from the `eas-build` repo.
# Test Plan
https://github.com/expo/eas-cli/pull/2220
* [ci] add update eas cli used on production for builds triggered with GitHub trigger once new version is published
* remove unnecessary docs from releasing
<!-- 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
Simplification, unification.
# How
Removed bare-specific template.
# Test Plan
None.
* test against node 20 and drop support for node 14
* update CHANGELOG.md
* update @types/node
* bump yarn version
* Revert "update @types/node"
This reverts commit 027e26b002.
* update @types/node
* try to debug
* Revert "try to debug"
This reverts commit 0d557d02f8.
* test sth
* update lock
* Revert "update lock"
This reverts commit 184b412655.
* Revert "test sth"
This reverts commit 77606cf5be.
* diff once again
* fix issues
* Revert "diff once again"
This reverts commit 526ab57453.
* Revert "[ENG-8956][eas-build] Improve EAS CLI tsconfig.json for local development (#1933)"
This reverts commit e963558ef6.
* add start-allow-unused option
* update CONTRIBUTING.md
* fix type error
<!-- 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
x-ref https://github.com/expo/eas-build/pull/302
# How
Upgraded `@expo/eas-build-job` and fixed the only TS error.
# Test Plan
None.
<!-- 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
I've noticed tests ran for an old commit even though I pushed a new one.
# How
Added `concurrency` where I thought it was applicable.
# Test Plan
None.
<!-- 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
It's nice to be able to download both application archive and "build artifact".
# How
Added `buildArtifactsUrl` to GraphQL query. It contains the thing I'm looking for.
# Test Plan
Ran `easd build:view 7bab0c66-d917-4873-9241-c5fa0b01dec1 --json` and confirmed it has the new field.
* [eas-cli] Add context fields for vcs clients
* [eas-cli] Replace vcs client helper with new context field
* [eas-cli] Pass instance of vcs client in helpers instead of re-calling vcs helper
* update CHANGELOG.md
* [FIX] Remove semver validation from node version read from .nvmrc
Node version can be specified as an alias (such as `iojs`, `lts/hydrogen` etc), so validating it as semver may cause errors for some users.
* update CHANGELOG.md
* fix(eas-cli): implement variadic `--platform` flag when creating EAS updates
* fix(eas-cli): finish todo and set minimum `@expo/[email protected]` version for multiple `--platform` flags during export
* update CHANGELOG.md
* fix(eas-cli): be verbose about `--platform=<flag>` in bundle script
* [eas-cli] handle server side defined error when `intel-medium` resource class is not available
* don't suggest using `intel-medium` in `eas.schema.json`
* update CHANGELOG.md
* update CHANGELOG.md
* [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
Changed noUnusedLocals and noUnusedParameters to false for easier local development and experimenting.
These checks do not run during local development. Instead, `yarn build` catches these cases on github.
Why
---
Fail fast with a clear message if the app config contradicts itself or the developer's behavior.
How
---
Throw if useClassicUpdates is set in the app config and the developer is running an EAS Update-related command or if the app config uses an EAS Update URL. If the developer is using a static app config (app.json), offer to modify the config file for them.
Test Plan
---
Added a unit test for ensureEASUpdateIsConfiguredAsync. Manually tested as wlel.
* added alias -m for --message
* align with the other messages
* updated README
* moving change in update/republish to a seperate PR
* removed README comment
* update CHANGELOG.md
---------
Co-authored-by: Steven Pu <[email protected]>
Co-authored-by: Steven Pu <[email protected]>
* added alias in republish
* reverted change in README
* update CHANGELOG.md
---------
Co-authored-by: Steven Pu <[email protected]>
Co-authored-by: Steven Pu <[email protected]>
* [eas-cli] validate that `expo-updates` are in project dependencies when somebody tries to run a build with channel set
* apply suggested changes
* remove unnecessary change
* fix warning
* improve validation logic
* improve insatlled message
* warn when expo-updates are in dev dependencies for update command
* impreve warn messsages
* improve warning messages
* one more warn message improvement
* update CHANGELOG.md
* [eas-cli][ENG-8763] Select default android keystore
- Add option to change default keystore from CLI (previously available only from dashboard)
- Streamline setting up new keystore
Instead of overwriting existing keystore, new one is created every time. Also, option to immediately set it as default is added, since it is also easier to change it from CLI.
* update CHANGELOG.md
<!-- 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
Cleanup after https://github.com/expo/eas-build/pull/233.
# How
Upgraded `@expo/steps` package. It is the only `eas-build` package in here.
# Test Plan
It's a type-only change so CI success will be enough.
* [eas-cli] make large resource class only available for paid users
* update eas.schema.json
* Revert "update eas.schema.json"
This reverts commit 319d998b76a4c6c87d137174d6cf9f90d64b3886.
* apply suggested changes
* update CHANGELOG.md
* [eas-cli][bugfix] Fix ios version-test
Tests were passing, but were not testing the right thing, essentially always defaulting to 'managed' workflow. `projectDir` should be set to the same value as EAS_PROJECT_ROOT.
* [eas-cli][ENG-8571] Validate CFBundleShortVersionString
* update CHANGELOG.md
* [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] don't resolve default resource class for iOS based on metadata
* don't set m1-medium as default in `eas build:configure`
* pass sdkVersion and reactNativeVersion in buildParams
* convert it to sync function
* update gql schema
* update CHANGELOG.md
* [eas-cli] allow users to select app to run if multiple apps are found in the build tarball
* rename variable
* improve error message
* apply suggested changes
* add dot
* update CHANGELOG.md
* [eas-cli] throw error if somebody tries to run iOS with `large` resource class selected through deprecated `--resource-class` flag
* apply suggested changes
* improve error message
* update CHANGELOG.md
* [eas-cli] Update apple utilities to avoid the maintenance error
* [eas-cli] Add changelog entry
* [eas-cli] Dont change the eas-cli version
* [eas-cli] Fix changelog entry
* [eas-cli] fix it again
* Unify error display method
Overriden the `Command`'s `catch` method to catch all the errors thrown by the commands, log the error message there the same way as it was previously handled in `src/build/build.ts` and re-throw generic `Error` instance with predefined base error message.
To avoid duplication, old `Log.error()` calls have been removed from `src/build/build.ts`.
Also added tests to see if the `catch()` method works as intended.
* Adjust base error messages
Base error messages have been adjusted after @dsokal suggested that the error may be caused by something different from a request and displaying message about a failed request is misleading
* update CHANGELOG.md
* Add test for unclean error message
Checks if the `[GraphQL] ` prefix gets removed when logging the error message
* Update handling GraphQL errors
Post-review update to how graphQL errors are handled
* Print different message for graphQL errors
When a graphQL error is caught a different base error message is printed
* Print original error to debug
When a graphQL error is caught and the message is cleaned, an original message is printed to debug (or just the same message otherwise)
* Add custom error classes
Created some custom error classes for known server side defined errors
* Log the error, not the message
Changed the debug log to log the error object, not the error message
* Fix
Fixed testing leftover
* Change phrasing
Edited the phrasing in default messages related to EAS Build
* Update if condition
Changed the if condition after review comment
* Create error base class
Created a new base class for the errors expected in build.ts, so they can be handled separately in `catch()`
* Move EasCommand properties
Moved the class properties above the class methods
* Remove helper method
Removed the helper method after review comment
* Change const type
Updated the type of SERVER_SIDE_DEFINED_ERRORS constant
* Change default base error message
Set the default base error message to `<command_name> command failed.`
* Remove comments
Removed leftover comments
* Change optional property
Changed empty string to optional property
* Post-review tweaks
Self-explanatory
* Fix failing test
One of tests started failing after changing the coalescing operators (|| -> ??). This fixes that test
See: https://linear.app/expo/issue/ENG-6945/improve-eas-cli-error-logging
* Remove error class
Removed `GenericGraphQLError` class after @wkozyra95 comment, since atm there's no need to handle it differently than a generic `Error`
See: https://linear.app/expo/issue/ENG-6945/improve-eas-cli-error-logging
* Move `EasCommandError` base class
Moved `EasCommandError` base class after @wkozyra95 comment. The class is not specific to `Build` command and so it has been moved to `commandUtils` directory
See: https://linear.app/expo/issue/ENG-6945/improve-eas-cli-error-logging
* Make message mandatory
Made `message` parameter in `EasCommandError`s mandatory, to remove need for providing a fallback string and making the server the source of truth for the errors messages
See: https://linear.app/expo/issue/ENG-6945/improve-eas-cli-error-logging
* Update packages/eas-cli/src/commandUtils/EasCommand.ts
Co-authored-by: Wojciech Kozyra <[email protected]>
* Move `baseGraphQLErrorMessage` property
Made the property into a constant in a global scope, since atm it is not changed in any of the subclasses
See: https://linear.app/expo/issue/ENG-6945/improve-eas-cli-error-logging
* Suppress ESLint warning
ESLint erroneously complains about the constructor of `EasCommandError` to be useless, which is not true is the constructor of `Error` parent class allows for optional `message` parameter and the constructor of `EasCommandError` does not
See: https://linear.app/expo/issue/ENG-6945/improve-eas-cli-error-logging
* Add error handling tests
Added a bunch of new tests related to the `handleBuildRequestError` function
See: https://linear.app/expo/issue/ENG-6945/improve-eas-cli-error-logging
* Directly export `handleBuildRequestError`
Dropped the `testExports` convention after team discussion
See: https://linear.app/expo/issue/ENG-6945/improve-eas-cli-error-logging
---------
Co-authored-by: Wojciech Kozyra <[email protected]>
* [eas-cli] link to build phase in error message
* add better fallback
* use fallback for all links
* use terminalLink.isSupported
* improvements after code review
* use old fallback
* update CHANGELOG.md
* [eas-cli] display build message data when picking build in `submit`, `build:run` and `build:resign` commands
* display only 200 first characters of message if it exists
* print only defined values
* add '...' to message if trimmed
* use array instead of object
* update CHANGELOG.md
* [eas-cli] fix issue with `eas.json` envs not available when resolving local config
* fix type definitions to prevent it from happening again
* update CHANGELOG.md
* [eas-cli] set `m1-medium` resource class for builds which don't specify resource class for SDK 48 and RN 0.71
* refactor resolveBuildResourceClassAsync function
* apply suggested changes
* drop warning for ios large resource classes
* call getDynamicProjectConfigAsync in create context function
* update CHANGELOG.md
* Revert "Revert "[eas-cli] Add missing key information about updates in json outputs (#1611)""
This reverts commit d20db0fff4.
* [eas-cli] Fix missing update fragment in publish mutation
* [docs] Update changelog to reflect the revert and new entry
Why
---
This reverts commit e42031eaef. A customer reported an issue with publishing updates.
How
---
Ran `git revert` and then re-generated the GraphQL schemas due to merge conflicts using `yarn generate-graphql-code`.
Test Plan
---
Automated tests. Ran `easd update --auto` in a test project.
* [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-cli] throw error when there are no emulator/simulator builds in `eas build:run` command
* handle missing build in correct place
* handle same error for latest flag
* add function to sanitize chosen build
* sanitize build selected by id
* improve build santization
* apply suggested improvements
* rename validation function
* update CHANGELOG.md
* [eas-cli] Use pagianted select prompt for eas build:run command
* apply suggestions from code review
* apply improvements from code review
* update CHANGELOG.md
* [eas-cli] Add test cases for republishing updates
* [eas-cli] Tweak the channel -> branch method errors to reuse in republish
* [eas-cli] Add support for --channel in update:republish
* [eas-cli] Add test cases to prevent using --group, --channel, or --branch together
* update CHANGELOG.md
* [eas-cli] Update the test case for resolving branch from channel
* [eas-cli] Add initial test cases for the update command
* [eas-cli] Add runtimeVersion option when mocking exports
* [eas-cli] Fix update flag validation for --branch and --channel
* [eas-cli] Add test case for --non-interactive, --channel, and --message
* update CHANGELOG.md
* [eas-cli] Fix linting issue
* [eas-cli] Reuse the input dir from the command
* [eas-cli] Explicitly mention the allowed flag combinations to avoid ambiguity
* [eas-cli] Move --auto to a distinct location in the error message
* [eas-cli] Fix linting issue
* Add --channel flag to eas update command
* use existing method
* adds undefined to return type
* move to getBranchNameFromChannelNameAsync.ts
* renames the function to singular "update"
* [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
* fix(update): add code signing support to republish and block different branches
* refactor(update): move codesigning info into update fragment
* update CHANGELOG.md
* fix(update): add code signing support to republish and block different branches
* refactor(update): mark group and republish flags as deprecated
* refactor(update): drop republish and group flags
* refactor(update): drop republish flag from command
* refactor(update): remove last republish code from update command
* refactor(update): either use --group or --branch in deprecation warning
* refactor(update): drop old runtime version from update command
* refactor(update): move asset variables closer to populated area
* fix(update): fix republish typo in deprecation warning
* fix(update): correct a merge conflict error related to publish query changes
* refactor(update): split out republish to separate command
* fix(update): add code signing support to republish and block different branches
* test(update): add missing republish command tests
* test(update): add test case without codesigning
* refactor(update): move codesigning info into update fragment
* refactor(update): make branch and group exclusive and simplify code
* update CHANGELOG.md
* [eas-cli] add caching for `eas build:run`
* cache in tmp directory
* use path from `path` instead of `node:path`
* don't hide eas build:run command
* apply feedback from review
* improvements after code review
* update CHANGELOG.md
* [eas-cli] add build:run support for Android
* add assertions about android executables
* use spawnAsync instead of spawn
* minor refactor
* minor improvements to prompts
* improve download function name
* refactor code after the review
* apply suggestions from the review
* fix commit message formatting
* use progress tracker instead of progress bar
* improve formatting of build choices
* fix typo in function name
* requested improvements
* test using path.join for fast-lob
* fix windows glob issues
* fix glob on windows
* allow users to run ios builds only on apple device
* use path.join instead of interpolation
* address feedback
* auto select android for non mac users
* minor improvements
* improve error messages
* update CHANGELOG.md
* fix(update): only create a channel with branch name when branch is created
* refactor(update): rename branchIsCreated to createdBranch
* update CHANGELOG.md
* [eas-cli] change choice formatting when selecting build to submit
* fix typo
* use description with one line choice
* use eas update channel vs old release channel
* update CHANGELOG.md
* feat: support uploading web bundles
Expo Router defaults to shipping with universal Metro support (ios, android, web) which means eas update breaks by default if it asserts that web is not supported.
This PR also fixes the inability to upload single platforms.
* ensure platform filtering works
* Update publish.ts
* add tests
* update CHANGELOG.md
* style xits from PR feedback
* attempt to fix
* fix
* Update index.ts
* Update CHANGELOG.md
* Update publish-test.ts
* Update publish-test.ts
* refactor(update): auto configure EAS updates when running eas update
* fix(update): make sure eas update does what it needs to do
* refactor(update): drop obsolete eas update validation errors
* refactor(update): drop duplicate truncate update message
* refactor(update): drop duplicate install expo-update message
* fix(update): use the old truncated update message limit
* refactor(update): ensure the latest changes are integrated in the PR
* fix(update): use the EAS update configured expo config
* chore(update): make the EAS Update outage a bit more readable
* fix(update): remove _internal from merged manifest if defined
* fix(update): make sure people can run `eas update:configure` without project id
* update CHANGELOG.md
* refactor(update): skip setting the sdkVersion when configuring
* fix(update): only merge nested objects when configuring
* fix(update): refetch the config whenever projects are auto-setup
* refactor(update): simplify the config object merging
* refactor(update): change logging based on review input
Co-authored-by: Evan Bacon <[email protected]>
* refactor(update): drop fyi .md extension from logging
Co-authored-by: Evan Bacon <[email protected]>
* refactor(update): alawys reload the project config after ensuring eas updates
* fix(update): linting issue caused by logging changes
* refactor(update): drop unused exports from updates configure code
* refactor(update): split merge config to separate method for testing
* fix(update): show full install log when debugging is enabled
* fix(update): add back the missing <remove this key> instruction
Co-authored-by: Evan Bacon <[email protected]>
* refactor(update): remove default non-interactive value to rely on falsy values
Co-authored-by: Will Schurman <[email protected]>
* refactor(updates): make non interactive optional to rely on falsy values
* Revert "refactor(update): remove default non-interactive value to rely on falsy values"
This reverts commit 23ac36d36e35b7a87724229234d41dcac8cf02db.
* Revert "refactor(updates): make non interactive optional to rely on falsy values"
This reverts commit 94ae7cc039c94f28b74a5cfd9857f79e5a11e82c.
* refactor(update): move ensure methods outside the update command
* fix(update): add back log about channel pointing to branch
* refactor(branch): reuse query from shared utilsin `branch:create`
* refactor(channel): reuse query from shared utilsin `channel:create`
Co-authored-by: Will Schurman <[email protected]>
* [eas-cli] Add flag sanitization in updates command
* refactor(update): remove default non-interactive value to rely on falsy values
Co-authored-by: Will Schurman <[email protected]>
* refactor(updates): make non interactive optional to rely on falsy values
* Revert "refactor(update): remove default non-interactive value to rely on falsy values"
This reverts commit 23ac36d36e35b7a87724229234d41dcac8cf02db.
* Revert "refactor(updates): make non interactive optional to rely on falsy values"
This reverts commit 94ae7cc039c94f28b74a5cfd9857f79e5a11e82c.
Co-authored-by: Will Schurman <[email protected]>
* [eas-cli] Warn about outdated build deployment when configuring EAS Update
* update changelog with PR number
* print warning no matter what
* Update packages/eas-cli/src/commands/update/configure.ts
Co-authored-by: Will Schurman <[email protected]>
Co-authored-by: Will Schurman <[email protected]>
* create eas run command
* improve run command
* downaload and install iOS sim app
* add logic to select best avaliable simulator
* add not implemented android command
* use expo cli implementation of detecting if simulator is running
* support both archive and app paths in path argument
* better validate path argument
* refactor iOS code
* assert that Xcode and xcrun are installed
* rename ios and android run files
* assert simulator app is installed
* apply suggestions from code review
* improve select sim build prompt
* hide command
* minor fixes
* apply improvements suggested in code review
* update CHANGELOG.md
* refactor: update ajv, add human errors, and prepare lint command
* feature: add custom validation rules
* refactor: allow metadata context to be created without auth state
* refactor: update validation errors with new custom issues
* refactor: update existing code to use new features
* feature: add custom apple validation rules
* feature: implement validation command with json option
* chore: clean up outdated files
* refactor: update config schema type to improve human error message
* [eas-cli] Fix typo in ajv version
* [eas-cli] Use built-in context API to get project dir
* [eas-cli] Remove commented code
* [eas-cli] Load project without enforcing project id in metadata:lint
* [eas-cli] Guard against faulty config objects
* update CHANGELOG.md
* docs(cli): fix keyword length typo
* refactor(cli): use optional chaining over ternary
Co-authored-by: Dominik Sokal <[email protected]>
* refactor(cli): drop non-null assertion in config resolver
* refactor(cli): drop implicit coercion in expressions
Co-authored-by: Dominik Sokal <[email protected]>
* refactor(cli): only initialize ajv when used
* refactor(cli): simplify error logging
* refactor(cli): move coascle to expodash as filter
* fix(cli): use proper empty check on readable errors
* refactor(cli): support non interactive in metadata lint
* refactor(cli): remove metadata context from lint command
* refactor(cli): split up metadata context into different methods
* refactor(cli): use profile instead of metadata path in config resolve methods
* refactor(cli): rename context to auth and simplify usage
* refactor(cli): move json schema files to top-level imports
* refactor(cli): use predicates in expodash filter instead of filter functions
* test(cli): update config tests to use mocked profile isntead
* test(cli): fix issue in filter predicate test
* [eas-cli] Reimplement the analytics manager
Co-authored-by: Dominik Sokal <[email protected]>
* [eas-cli] Replace secret:list table with format fields
* update CHANGELOG.md
* [eas-cli] Replace created at with update in secrets list
Co-authored-by: Dominik Sokal <[email protected]>
* Revert updated at
Co-authored-by: Dominik Sokal <[email protected]>
* [eas-cli] use env variable to select M1 resource class
* [eas-cli] create `m1-experimental` option for `--resource-class` flag
* improvements after code review
* throw an error instead of using oclif/errors in resolveResourceClass function
* update CHANGELOG.md
* [eas-cli] provide suggestions for developers when archive size is large
* use learn more function
* apply suggestion from review
* apply suggestions from code review
* update CHANGELOG.md
* [eas-cli] add `-e` flag as a shortcut for `--profile` flag
* revert readme changes
* add description for profile flag on config command
* update CHANGELOG.md
<!-- Thanks for contributing to _EAS CLI_! Before you submit your pull request, please make sure to check the following boxes by putting an x in the [ ] (don't: [x ], [ x], do: [x]) -->
# Checklist
- [ ] I've added an entry to [CHANGELOG.md](https://github.com/expo/eas-cli/blob/main/CHANGELOG.md#main) if necessary. You can comment this pull request with `/changelog-entry [breaking-change|new-feature|bug-fix|chore] [message]` and CHANGELOG.md will be updated automatically.
<!-- 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". -->
message:${{ contains(github.event.pull_request.labels.*.name, 'no changelog') && '⏩ The changelog entry check has been skipped since the "no changelog" label is present.' || '✅ Thank you for adding the changelog entry!' }}
message-failure:|
❌ It looks like a changelog entry is missing for this PR. Add it manually to CHANGELOG.md.
⏩ If this PR doesn't require a changelog entry, such as if it's an internal change that doesn't affect the user experience, you can add the "no changelog" label to the PR.
# packages are ordered according to output of `lerna list --toposort`
# https://github.com/expo/turtle-v2/pull/568
for PACKAGE in "@expo/downloader" "@expo/eas-build-job" "@expo/logger" "@expo/template-file" "@expo/steps" "@expo/turtle-spawn" "@expo/build-tools"; do
1. Run `yarn release` in the repository root folder.
2. That's it! GitHub Actions is going to take care of the rest. Watch the #eas-cli Slack channel for a successful release notification.
Set up an alias for the EAS CLI so you can try it in projects all around your computer. The project is compiled on the fly so you don't need to run a build (watch) command.
> The only exception is when you just cloned the repository or there have been changes in `packages/eas-json`. In that case, you'll have to run `yarn build` in the root.
Open your `.zshrc` or other config file and add:
```
alias easd="/PATH/TO/eas-cli/bin/run"
```
Then use it with `easd` like `easd build`.
If you're making changes to `packages/eas-json` or prefer/need to work with production code, start the build command in watch mode with:
```
yarn start
```
If it is easier for you to work with the code locally with compiler options set to:
```json
...
"compilerOptions":{
...
"noUnusedLocals":false,
"noUnusedParameters":false,
...
}
...
```
you can consider using:
```
yarn start-allow-unused
```
## Format
- Be sure to update the [`CHANGELOG.md`](./CHANGELOG.md) with changes for every PR. There is a changelog bot that can generate the proper entry for you. The instructions on how to use it are in the PR description placeholder.
- End `async` functions with `Async` like `runAsync`. This is just how we format functions at Expo.
- Utilize the unified `Log` module instead of `console.log`.
## Using local and staging API
For development against local API:
- Set up the API server as described at https://github.com/expo/universe/tree/main/server/www.
- Set the `EXPO_LOCAL=1` env variable either on every command run (e.g. `EXPO_LOCAL=1 easd ...`) or more permamently with `export EXPO_LOCAL=1` (works in a current shell session).
For development against staging API:
- Set the `EXPO_STAGING=1` env variable either on every command run (e.g. `EXPO_STAGING=1 easd ...`) or more permamently with `export EXPO_STAGING=1` (works in a current shell session).
## Working on local builds (`eas build --local`)
See https://github.com/expo/eas-build/blob/main/DEVELOPMENT.md for how to set up your environment when making changes to [`eas-cli-local-build-plugin`](https://github.com/expo/eas-build/tree/main/packages/local-build-plugin) and/or [`build-tools`](https://github.com/expo/eas-build/tree/main/packages/build-tools).
## Testing
Run `yarn test` either in the repository root or in a package directory that you're working on.
1. Run `yarn release` in the repository root folder. The next version is chosen automatically based on the changelog entries. If you want to use different version, pass the version string as a positional argument to the command, e.g. `yarn release 1.2.3`.
2. That's it! GitHub Actions is going to take care of the rest. Watch the #eas-cli Slack channel for a successful release notification.
## Choosing the next version
As stated above, the next EAS CLI version is chosen automatically based on the existing changelog entries under the unreleased section in **CHANGELOG.md**.
The algorithm works as follows:
- If there are any entries in the "🛠 Breaking changes" section, bump the MAJOR version.
- Otherwise, if there are any entries in the "🎉 New features", bump the MINOR version.
"description":"When parents visit the Kids category on the App Store, they expect the apps they find will protect their children’s data, provide only age-appropriate content, and require a parental gate in order to link out of the app, request permissions, or present purchasing opportunities. It’s critical that no personally identifiable information or device information be transmitted to third parties, and that advertisements are human-reviewed for age appropriateness in order to be displayed.\n@see https://developer.apple.com/news/?id=091202019a",
"markdownDescription":"When parents visit the Kids category on the App Store, they expect the apps they find will protect their children’s data, provide only age-appropriate content, and require a parental gate in order to link out of the app, request permissions, or present purchasing opportunities. It’s critical that no personally identifiable information or device information be transmitted to third parties, and that advertisements are human-reviewed for age appropriateness in order to be displayed.\n\n[Learn more](https://developer.apple.com/news/?id=091202019a)"
"description":"When parents visit the Kids category on the App Store, they expect the apps they find will protect their children’s data, provide only age-appropriate content, and require a parental gate in order to link out of the app, request permissions, or present purchasing opportunities. It’s critical that no personally identifiable information or device information be transmitted to third parties, and that advertisements are human-reviewed for age appropriateness in order to be displayed.\n@see https://developer-mdn.apple.com/news/?id=091202019a",
"markdownDescription":"When parents visit the Kids category on the App Store, they expect the apps they find will protect their children’s data, provide only age-appropriate content, and require a parental gate in order to link out of the app, request permissions, or present purchasing opportunities. It’s critical that no personally identifiable information or device information be transmitted to third parties, and that advertisements are human-reviewed for age appropriateness in order to be displayed.\n\n[Learn more](https://developer-mdn.apple.com/news/?id=091202019a)"
},
"seventeenPlus":{
"type":"boolean",
"deprecated":true,
"deprecationMessage":"This property is deprecated, use `ageRatingOverride` instead.",
"description":"If your app rates 12+ or lower, and you believe its content may not be suitable for children under 17, you can manually set the age rating to 17+.\n@see https://help.apple.com/app-store-connect/#/dev599d50efb",
"markdownDescription":"If your app rates 12+ or lower, and you believe its content may not be suitable for children under 17, you can manually set the age rating to 17+.\n\n[Learn more](https://help.apple.com/app-store-connect/#/dev599d50efb)"
"description":"If your app rates 12+ or lower, and you believe its content may not be suitable for children under 17, you can manually set the age rating to 17+.\n\nIf your app will be distributed through alternative app marketplaces or websites in the European Union and you believe your app is [Unrated](https://developer.apple.com/help/app-store-connect/reference/age-ratings), set this to `UNRATED`.\n\n@see https://help.apple.com/app-store-connect/#/dev599d50efb",
"markdownDescription":"If your app rates 12+ or lower, and you believe its content may not be suitable for children under 17, you can manually set the age rating to 17+.\n\nIf your app will be distributed through alternative app marketplaces or websites in the European Union and you believe your app is [Unrated](https://developer.apple.com/help/app-store-connect/reference/age-ratings), set this to `UNRATED`.\n\n[Learn more](https://help.apple.com/app-store-connect/#/dev599d50efb)"
"description":"If your app rates 12+ or lower, and you believe its content may not be suitable for children under 15 or 19, you can manually set the age rating to 15+ or 19+.\n\nIf your app will be distributed through alternative app marketplaces or websites in the European Union and you believe your app is [Unrated](https://developer.apple.com/help/app-store-connect/reference/age-ratings), set this to `UNRATED`.\n\n@see https://help.apple.com/app-store-connect/#/dev599d50efb",
"markdownDescription":"If your app rates 12+ or lower, and you believe its content may not be suitable for children under 15 or 19, you can manually set the age rating to 15+ or 19+.\n\nIf your app will be distributed through alternative app marketplaces or websites in the European Union and you believe your app is [Unrated](https://developer.apple.com/help/app-store-connect/reference/age-ratings), set this to `UNRATED`.\n\n[Learn more](https://help.apple.com/app-store-connect/#/dev599d50efb)"
},
"lootBox":{
"type":"boolean",
"description":"Does your app contain purchasable loot boxes? These virtual containers provide players with in-game items, including functional cards or cosmetic modifications, based on random chance."
}
}
},
@@ -565,6 +600,20 @@
"maxLength":4000
}
}
},
"AppleAgeRatingOverride":{
"enum":[
"NONE",
"SEVENTEEN_PLUS",
"UNRATED"
]
},
"AppleKoreaAgeRatingOverride":{
"enum":[
"NONE",
"FIFTEEN_PLUS",
"NINETEEN_PLUS"
]
}
},
"AppleConfig":{
@@ -775,19 +824,5 @@
}
}
}
},
"properties":{
"configVersion":{
"const":0,
"description":"The EAS metadata store configuration version"
exports[`BuildVersionGetView reading version aborts when the appVersionSource is not specified and the user chooses to set it to LOCAL 1`] = `"Aborting..."`;
exports[`BuildVersionGetView reading version when appVersionSource is set to local 1`] = `"This project is not configured for using remote version source. Add [1m{"cli": { "appVersionSource": "remote" }}[22m in eas.json or re-run this command without "--non-interactive" flag."`;
test('reading version sets appVersionSource to LOCAL and aborts when the appVersionSource is not specified and is run in non-interactive mode',async()=>{
test('setting version aborts when the appVersionSource is not specified and the user chooses to set it to LOCAL, and they refuse auto configuration',async()=>{
test('setting version when the appVersionSource is not specified and the user chooses to set it to LOCAL, and they allow auto configuration',async()=>{
ACTION='action',// generic event type which is used to determine the 'daily active user' stat, include an `action: eas ${subcommand}` property inside of the event properties object
ACTION='action',// generic event type which is used to determine the 'daily active user' stat, include an `action: eas ${subcommand}` property inside of the event properties object
* @param {function} options.filterPredicate - A predicate to filter the branches that are shown to the user. It takes a branchInfo object as a parameter and returns a boolean.
* @param {string} options.printedType - The type of branch printed to the user. Defaults to 'branch'.
* @param {number} options.pageSize - The number of branches to show per page. Defaults to 100.
* @param {function} options.beforeEachFilterQuery Optional. If a filter predicate was specified, this callback function will be called before each query.
* @args externalQueryParams The query params for the pagination.
* @args totalNodesFetched The total number of nodes fetched so far.
* @args dataset The dataset so far.
* @param {function} options.afterEachFilterQuery Optional. If a filter predicate was specified, this callback function will be called after each query.
* @args externalQueryParams The query params for the pagination.
* @args totalNodesFetched The total number of nodes fetched so far.
* @args dataset The dataset so far.
* @args willFetchAgain If the query will fetch again to get a complete page.
constEXPECTED_EAS_BUILD_DOWN_MESSAGE=`EAS Build is down for maintenance. Try again later. Check ${link(
'https://status.expo.dev/'
)} for updates.`;
constEXPECTED_MAX_BUILD_COUNT_MESSAGE_ANDROID=`You have already reached the maximum number of pending Android builds for your account. Try again later.`;
constEXPECTED_MAX_BUILD_COUNT_MESSAGE_IOS=`You have already reached the maximum number of pending iOS builds for your account. Try again later.`;
constEXPECTED_GENERIC_MESSAGE=
'Build request failed. Make sure you are using the latest eas-cli version. If the problem persists, report the issue.';
`Remote versions are not configured and EAS CLI was not able to read the current version from your project. Use "eas build:version:set" to initialize remote versions.`
@@ -212,18 +230,23 @@ export async function resolveRemoteVersionCodeAsync({
@@ -316,8 +479,8 @@ async function handleSingleBuildProgressAsync(
spinner.succeed('Build finished');
return{refetch: false};
caseBuildStatus.New:
spinner.text=`Build is waiting to enter the queue. Check your concurrency limit at ${chalk.underline(
formatAccountSubscriptionsUrl(accountName)
spinner.text=`Build concurrency limit reached for your account. Build will enter queue once a concurrency becomes available. Add additional concurrencies at ${link(
formatAccountBillingUrl(accountName)
)}.`;
break;
caseBuildStatus.InQueue:{
@@ -330,18 +493,20 @@ async function handleSingleBuildProgressAsync(
`The following environment variables are defined in both the "${buildProfileName}" build profile "env" configuration and the "${environment.toLowerCase()}" environment on EAS: ${overlappingKeys.join(
', '
)}. The values from the build profile configuration will be used.`
);
}
}
Log.newLine();
return{...serverEnvVars,...buildProfile.env};
}catch(e){
Log.error(`Failed to pull env variables for environment ${environment} from EAS servers`);
Log.error(e);
Log.error(
'This can possibly be a bug in EAS/EAS CLI. Report it here: https://github.com/expo/eas-cli/issues'
`The required format for "version" field from app.json/app.config.ts for App Store iOS builds is one to three period-separated integers, such as 10.14.1. The string can only contain numeric characters (0-9) and periods. Current value: ${shortVersion}. Edit the "version" field in your app.json/app.config.ts to match the format required by Apple. ${learnMore(
`The required format for "CFBundleShortVersionString" in Info.plist for App Store iOS builds is one to three period-separated integers, such as 10.14.1. The string can only contain numeric characters (0-9) and periods. Current value: ${shortVersion}. Edit the "CFBundleShortVersionString" in your Info.plist to match the format required by Apple. ${learnMore(
`Remote versions are not configured and EAS CLI was not able to read the current version from your project. Use "eas build:version:set" to initialize remote versions.`
@@ -302,18 +351,23 @@ export async function resolveRemoteBuildNumberAsync({
`The "image" field in the build profile "${buildProfile.profileName}" is set to "${buildProfile.profile.image}". This tag is deprecated and will be removed in the future. Use other images or tags listed here: https://docs.expo.dev/build-reference/infrastructure/`
);
}elseif(
buildProfile.profile.image&&
[
'ubuntu-20.04-jdk-11-ndk-r19c',
'ubuntu-20.04-jdk-8-ndk-r19c',
'ubuntu-20.04-jdk-11-ndk-r21e',
'ubuntu-20.04-jdk-8-ndk-r21e',
'ubuntu-22.04-jdk-8-ndk-r21e',
'ubuntu-20.04-jdk-11-ndk-r23b',
].includes(buildProfile.profile.image)
){
Log.warn(
`The "image" field in the build profile "${buildProfile.profileName}" is set to "${
buildProfile.profile.image
}". This image is deprecated and will be removed on September 1st, 2024. ${learnMore(
`The build profile "${buildProfile.profileName}" uses the channel "${buildProfile.profile.channel}", but you've added "expo-updates" as a dev dependency. To make channels work for your builds, move "expo-updates" from dev dependencies to the main dependencies in your project.`
);
}elseif(nonInteractive){
Log.warn(
`The build profile "${buildProfile.profileName}" has specified the channel "${buildProfile.profile.channel}", but the "expo-updates" package hasn't been installed. To use channels for your builds, install the "expo-updates" package by running "npx expo install expo-updates" followed by "eas update:configure".`
);
}else{
Log.warn(
`The build profile "${buildProfile.profileName}" specifies the channel "${buildProfile.profile.channel}", but the "expo-updates" package is missing. To use channels in your builds, install the "expo-updates" package and run "eas update:configure".`
);
constinstallExpoUpdates=awaitconfirmAsync({
message:`Would you like to install the "expo-updates" package and configure EAS Update now?`,
});
if(installExpoUpdates){
awaitensureEASUpdateIsConfiguredAsync({
exp,
projectId,
projectDir,
platform: RequestedPlatform.All,
vcsClient,
env,
});
Log.withTick('Installed expo-updates and configured EAS Update.');
thrownewError('Command must be re-run to pick up new updates configuration.');
`Build profile specifies the "${profileResourceClass}" resource class but you passed "${resourceClassFlag}" to --resource-class.\nUsing "${resourceClassFlag}" as the override.`
`Experimental "large" resource class for Intel iOS workers is no longer available. Remove the specified resource class to use the default, or learn more about all available resource classes: ${link(
'https://docs.expo.dev/build-reference/eas-json/'
)}`
);
}
if(ResourceClass.M1_MEDIUM===resourceClass){
Log.warn(
`Resource class ${chalk.bold(resourceClass)} is deprecated. Use ${chalk.bold(
'm-medium'
)} instead.`
);
}
if(ResourceClass.M_LARGE===resourceClass){
Log.warn(
`Resource class ${chalk.bold(resourceClass)} is deprecated. Use ${chalk.bold(
Loaded 100 of 778 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.