[eas-cli] Use production mode for Expo Updates commands - #4229
Open
ramonclaudio wants to merge 6 commits into
Open
[eas-cli] Use production mode for Expo Updates commands#4229ramonclaudio wants to merge 6 commits into
ramonclaudio wants to merge 6 commits into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## @ramonclaudio/dvt-119-eas-config-mode-handoff #4229 +/- ##
=================================================================================
+ Coverage 63.86% 63.88% +0.03%
=================================================================================
Files 1032 1033 +1
Lines 47511 47535 +24
Branches 9993 9999 +6
=================================================================================
+ Hits 30338 30365 +27
+ Misses 17072 17069 -3
Partials 101 101 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
ramonclaudio
force-pushed
the
@ramonclaudio/dvt-119-eas-cli-env-mode
branch
from
August 19, 2026 18:52
bd26e60 to
5edf5bf
Compare
ramonclaudio
marked this pull request as ready for review
August 19, 2026 19:23
|
Subscribed to pull request
Generated by CodeMention Warning: The preamble and epilogue options in commentConfiguration are deprecated. Use template instead. |
ramonclaudio
force-pushed
the
@ramonclaudio/dvt-119-eas-cli-env-mode
branch
from
August 21, 2026 14:20
77ab8a7 to
743749d
Compare
|
✅ Thank you for adding the changelog entry! |
This was referenced Aug 21, 2026
ramonclaudio
marked this pull request as ready for review
August 21, 2026 17:37
Member
Author
|
@expo-bot verify |
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.
Stacked on #4180.
Why
EAS CLI can use an existing
NODE_ENVwhen it resolves the runtime version or syncs Expo Updates config, which can make it load different env files for the same build. EAS CLI can also pass dotenv values loaded by a parent process to Expo Updates, which can make Expo Updates reuse values from a different mode.How
I updated the Expo Updates commands to use
productionmode for runtime version resolution and Android and iOS config sync, and kept the original EAS CLI env unchanged. EAS CLI still supports Node 20.0.0, but@expo/envv2.5.0 requires Node 20.12.0, so I added the inherited dotenv cleanup locally for now.Test Plan
Tests and package checks pass.