[eas-cli] Pass env from process.env and build profile to expo-updates CLI calls where applicable #2359
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 is the eas-cli equivalent of expo/eas-build#388.
Essentially, when getting the project config in expo-updates CLI, the env must be supplied.
How
Pass the env to the
spawnAsync
. Note that this passes the build profile env when possible as well (only in build command).Test Plan
Still need to come up with a test plan here. I think it will be:
yarn create expo-app --template default@beta
)eas init
,eas update:configure
,eas build:configure
eas build -p android
, see it fails (current prod version of eas-cli)neas build -p android
, see it succeeds.