-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
chore: validate env expo cp-7.63.0 #25415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+175
−133
Merged
Changes from 4 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
0cd1525
chore: fix ota env exporting
weitingsun 7d4dd4d
move create .env back to push-eas-update.yml
weitingsun 7d24363
Merge branch 'main' into chore/validate-env-expo
weitingsun 1665c61
add env variables with empty values
weitingsun 2c73880
print off first 3 characters of the env val
weitingsun 4d92ae7
move .env creation back to build.sh
weitingsun 3d4e4ac
fix spacing
weitingsun 895e26c
add .env back to push-eas-update.yml
weitingsun 39ad433
fix parsing error
sethkfman d29cc49
run builds sequentially
sethkfman 41826f4
add platform as an input to push ota update
weitingsun c8746b7
exit if expo token is not set
weitingsun faa3f6b
fix platform variable bug
weitingsun File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Environment values lack escaping for special characters
Low Severity
The new
.envcreation writes values without escaping or quoting:echo "${var}=${value}". The removedcreateEnvFile()function properly escaped backslashes, double quotes, and dollar signs, then wrapped values in quotes. If any secret values contain special characters (like$,",\, or spaces), they could cause parsing issues when Expo reads the.envfile or trigger unintended shell expansion.