feat(expo): release, promote, patch and roll back Expo Updates apps - #15
Merged
Merged
Conversation
This file contains hidden or 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
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.
Adds support for apps that use
expo-updatesinstead of the CodePush SDK.dpctl release-expo MyExpoApp -d productionRuns
npx expo export, packages iOS and Android, uploads both.--exportDirreleases an export built earlier instead, e.g. from a previous CI step.promote,patchandrollbacknow check the app's platform and take the Expo route forexpo-v1apps. Nothing changes for CodePush apps.Rollback is the interesting one. A channel serves one release per platform and runtime version, so it rolls back each unless you narrow it with
--platformor--runtimeVersion. It republishes the previous release rather than just disabling the bad one, sinceexpo-updatesonly loads an update newer than the one it launched. If there's nothing good to go back to,--toEmbeddedsends devices to the bundle in the store binary.