-
Notifications
You must be signed in to change notification settings - Fork 86
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
[eas-cli] Use expo-updates runtime version CLI to generate runtime versions #2251
Conversation
Size Change: -2.64 kB (0%) Total Size: 51.3 MB
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2251 +/- ##
==========================================
+ Coverage 54.02% 54.05% +0.03%
==========================================
Files 519 520 +1
Lines 18935 18953 +18
Branches 3798 3805 +7
==========================================
+ Hits 10228 10243 +15
- Misses 8686 8689 +3
Partials 21 21 ☔ View full report in Codecov by Sentry. |
057d5ee
to
d75380a
Compare
bdb7cb0
to
edaa89f
Compare
edaa89f
to
0fbfd1f
Compare
/changelog-entry bug-fix Use expo-updates runtime version CLI to generate runtime versions |
✅ Thank you for adding the changelog entry! |
Why
This makes use of expo/expo#27263 to generate the correct runtime version for build metadata and updates.
How
Call the command in the package to use the versioned config-plugins for the app. This way the runtime version is consistent no matter what version of eas-cli is used (and for canary versions so we don't have to update eas-cli to use canaries).
Test Plan
Run tests.
Manual test:
neas build
with a bare-app in expo/exponeas update
with same app, including withEXPO_DEBUG=1
to see fingerprint sources.