[docs] Add publish an update guide and other changes #27665
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
📘 Your docs preview website is ready! |
brentvatne
reviewed
Mar 15, 2024
brentvatne
approved these changes
Mar 15, 2024
quinlanj
approved these changes
Mar 15, 2024
Co-authored-by: Quinlan Jung <quin@expo.io>
amandeepmittal
commented
Mar 20, 2024
amandeepmittal
commented
Mar 20, 2024
|
|
||
| Publishing an update allows: | ||
| - Fixing bugs and quickly updating non-native parts of a project instead of creating a new build | ||
| - [Sharing a preview version of an app](/review/overview/) using internal distribution |
There was a problem hiding this comment.
@brentvatne, as per your recent feedback, I've added a link to Review > Overview that mentions sharing a preview version.
3 tasks
amandeepmittal
commented
Mar 26, 2024
amandeepmittal
commented
Mar 29, 2024
amandeepmittal
added a commit
that referenced
this pull request
Mar 31, 2024
…Extensions tab (#27772) # Why <!-- Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests. --> Closes ENG-11705 # How <!-- How did you build this feature or fix this bug and why? --> This PR updates the Use expo-dev-client with EAS Update guide by: - Adding info on what **Extensions** tab is and how it can be used to preview an update in a development build - Move the Construct a specific URL into its own section - Update introduction to match the contents of the guide and explain what this guide does for the reader - Change title of "More" section to "Example" since it only provides a link to the GitHub example - Change the title of this doc to "Load a published update with expo-dev-client and EAS Update" to match the contents of the guide - Link to publish update guide from #27665 when it mentions about publishing an update - Update `BoxLink` description to use inline code syntax highlight for the library name # 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. --> Run docs locally and visit: http://localhost:3002/eas-update/expo-dev-client/ or see Preview: http://docs.expo.dev-pr-27772.s3-website-us-east-1.amazonaws.com/eas-update/expo-dev-client/. # 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).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
This came up recently in a conversation with @brentvatne as we do not have a page where we describe how to publish an update and how it works briefly.
How
In the EAS Update section, this PR:
Other changes:
Test Plan
Run docs locally and visit: http://localhost:3002/eas-update/publish/ or see preview: http://docs.expo.dev-pr-27665.s3-website-us-east-1.amazonaws.com/eas-update/publish/.
Checklist
npx expo prebuild& EAS Build (eg: updated a module plugin).