[ENG-9473] Document new build option: pnpm (#24227)# Why https://linear.app/expo/issue/ENG-9473/support-setting-pnpm-version-with-easjson
[docs] final docs improvements before launching custom builds (#23901)# Why Add info about how user can use built-in function to create their own build. Add `withoutCredentials` to `eas.json` s
[docs] final docs improvements before launching custom builds (#23901)# Why Add info about how user can use built-in function to create their own build. Add `withoutCredentials` to `eas.json` schema. # How Add info about how user can use built-in function to create their own build. Add `withoutCredentials` to `eas.json` schema. # Test Plan Preview # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
show more ...
[docs][updates] Clarify when channel is null/ how channel in eas.json relates to dev build (#23783)# Why Had a support request re: some confusion about when `Updates.channel` is populated. User s
[docs][updates] Clarify when channel is null/ how channel in eas.json relates to dev build (#23783)# Why Had a support request re: some confusion about when `Updates.channel` is populated. User suggested this would be good to have in the docs. # How At first I just added a clarification about Expo Go/ dev builds and `channel` in the `expo-updates` API. Then I thought of how the **eas.json** schema can further explain how `devClient` affects `channel` (which affects `Updates.channel`). An, in turn, how `channel` and `releaseChannel` could further account for the Classic Updates sunset. # Test Plan Looked at docs. # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
[docs] add info about `rollout` property for Android submit profile (#23695)# Why Companion to https://github.com/expo/eas-cli/pull/1938 # How Add info about `rollout` property for Android
[docs] add info about `rollout` property for Android submit profile (#23695)# Why Companion to https://github.com/expo/eas-cli/pull/1938 # How Add info about `rollout` property for Android submit profile # Test Plan <!-- Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction. --> # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
[docs][ENG-8521] Rearrange information about VM specs (#22601)# Why Docs should use data from `eas-build` repo (https://github.com/expo/eas-build/pull/250) to generate hardware and vm specs.
[docs][ENG-8521] Rearrange information about VM specs (#22601)# Why Docs should use data from `eas-build` repo (https://github.com/expo/eas-build/pull/250) to generate hardware and vm specs. # Deploy Plan 1. https://github.com/expo/eas-build/pull/250 2. https://github.com/expo/expo/pull/22601 3. https://github.com/expo/universe/pull/12701 --------- Co-authored-by: Szymon Dziedzic <[email protected]>
[docs] Cut SDK 49 beta docs
[ENG-9026][docs] better eas update file names (#22979)# Why If an EAS Update doc has a verbose path, rename it to something equivalent, but shorter # Checklist <!-- Please check the appr
[ENG-9026][docs] better eas update file names (#22979)# Why If an EAS Update doc has a verbose path, rename it to something equivalent, but shorter # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
[docs] make `large` resource class only available for paid tier plans (#22536)# Why Companion to https://github.com/expo/universe/pull/12375 # How Update `eas.json` schema docs. # Test
[docs] make `large` resource class only available for paid tier plans (#22536)# Why Companion to https://github.com/expo/universe/pull/12375 # How Update `eas.json` schema docs. # Test Plan <!-- Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction. --> # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
[docs] fix broken links reported by Next in build log (#22499)
[docs] mention `large` resource class for iOS in `eas.json` schema (#22313)# Why Companion to https://github.com/expo/eas-cli/pull/1817 # How Add info about the `large` resource class for
[docs] mention `large` resource class for iOS in `eas.json` schema (#22313)# Why Companion to https://github.com/expo/eas-cli/pull/1817 # How Add info about the `large` resource class for iOS to our infrastructure docs and `eas.json` reference # Test Plan <!-- Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction. --> # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
[docs] [ENG-8120] Rename `cache.customPaths` to `cache.paths` in eas.json (#22220)Adjusted all references of `cache.customPaths` to mention the actual name of the field which is `cache.paths` #
[docs] [ENG-8120] Rename `cache.customPaths` to `cache.paths` in eas.json (#22220)Adjusted all references of `cache.customPaths` to mention the actual name of the field which is `cache.paths` # Why <!-- Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests. --> After disabling the default caching in EAS Build, it doesn't make much sense to keep a field called `cache.customPaths` (since there are no more default paths) and it was decided to replace it with just `cache.paths`. Here I update the docs to reflect that change See: https://linear.app/expo/issue/ENG-8120/rename-cachecustompaths-to-cachepaths-in-easjson-and-job-schema # How <!-- How did you build this feature or fix this bug and why? --> Adjusted all references of `cache.customPaths` to mention the actual name of the field which is `cache.paths` # Test Plan <!-- Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction. --> Tested manually by running the dev server - `/build-reference/caching/` <img width="1103" alt="Screenshot 2023-04-21 at 14 36 13" src="https://user-images.githubusercontent.com/2974455/233637817-556cc9dc-09e6-4ab4-bfda-db3a000dc1e4.png"> - `/build-reference/eas-json/#cache` <img width="1103" alt="Screenshot 2023-04-21 at 14 35 50" src="https://user-images.githubusercontent.com/2974455/233637885-5452ca2c-b3e0-4587-9c30-1c42d0b4aed7.png"> # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
[constants] Remove references to Constants.manifest (#22070)
[ENG-7968][docs] add info about how user can cache `Podfile.lock` across builds (#21997)# Why https://linear.app/expo/issue/ENG-7968/do-not-cache-podfilelock-by-default Companion to https:/
[ENG-7968][docs] add info about how user can cache `Podfile.lock` across builds (#21997)# Why https://linear.app/expo/issue/ENG-7968/do-not-cache-podfilelock-by-default Companion to https://github.com/expo/turtle-v2/pull/1256 We are planning to stop caching `Podfile.lock` by default, so it would be helpful to explain to users how they can enable it for themselves. # How Explain how users can enable caching `Podfile.lock` # Test Plan Run docs locally # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
[ENG-7676][docs] update docs about `default` and `medium` resource classes (#21731)# Why https://linear.app/expo/issue/ENG-7709/create-m-large-and-m-medium-resource-classes # How Update
[ENG-7676][docs] update docs about `default` and `medium` resource classes (#21731)# Why https://linear.app/expo/issue/ENG-7709/create-m-large-and-m-medium-resource-classes # How Update description of `default` and `medium` resource classes for iOS
[ENG-7709][ci][docs] use `m-medium` resource class instead of deprecated `m1-medium` resource class (#21730)# Why We deprecated the `m1-medium` resource class and added the `m-medium` resource
[ENG-7709][ci][docs] use `m-medium` resource class instead of deprecated `m1-medium` resource class (#21730)# Why We deprecated the `m1-medium` resource class and added the `m-medium` resource class. # How Use the `m-medium` resource class instead of the `m1-medium` resource class in the build reference. Use `m-medium` in CI jobs running on EAS.
[docs] remove dropped SDK 45 docs, remove SDK 45 references (#21402)
[docs] Remove classic build references in app config schema & sync changes to docs (#21230)
[docs] Add SDK 48
[docs] Update Hermes guide to state that Hermes is the new default engine (#21047)# Why Follow up of https://github.com/expo/expo/pull/21001 Closes [ENG-7163](https://linear.app/expo/issue/ENG-
[docs] Update Hermes guide to state that Hermes is the new default engine (#21047)# Why Follow up of https://github.com/expo/expo/pull/21001 Closes [ENG-7163](https://linear.app/expo/issue/ENG-7163) # How Update `Using Hermes Engine` guide to state that Hermes is the new default engine, aligns `ExpoConfig` types and app-config schema with the server ```sh # inside packages/@expo/config-types/ yarn generate --path /../../../../../../universe/server/www/xdl-schemas/UNVERSIONED-schema.json # inside docs/ yarn run schema-sync unversioned ``` # Test Plan N / A # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Aman Mittal <[email protected]>
[ENG-7222][docs] add resource class related documentation for EAS Build (#20928)# Why The resource class documentation wasn't properly updated in a while. # How Update information about re
[ENG-7222][docs] add resource class related documentation for EAS Build (#20928)# Why The resource class documentation wasn't properly updated in a while. # How Update information about resource classes used in EAS Build. # Test Plan Test locally # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
[config-plugins][config-types] align with server schema (#20895)# Why Follow up of https://github.com/expo/universe/pull/11245 Closes ENG-4613 # How This PR Aligns `ExpoConfig` types an
[config-plugins][config-types] align with server schema (#20895)# Why Follow up of https://github.com/expo/universe/pull/11245 Closes ENG-4613 # How This PR Aligns `ExpoConfig` types and app-config schema with the server ```sh # inside packages/@expo/config-types/ yarn generate --path /../../../../../../universe/server/www/xdl-schemas/UNVERSIONED-schema.json # inside docs/ yarn run schema-sync unversioned ``` # Test Plan Tests should pass # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
[ENG-7158][ENG-7060][docs] add `resourceClass` field to eas json schema (#20773)# Why https://linear.app/expo/issue/ENG-7158/add-resourceclass-to-build-profile https://linear.app/expo/issue/E
[ENG-7158][ENG-7060][docs] add `resourceClass` field to eas json schema (#20773)# Why https://linear.app/expo/issue/ENG-7158/add-resourceclass-to-build-profile https://linear.app/expo/issue/ENG-7060/addupdate-resource-class-names # How Add information about new `resourceClass` field in eas json schema # Test Plan Test locally # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
[docs] move schemas to `static`, use JSON instead (#20641)