Repository navigation
chore: bump example Expo for CI compatibility - #14
Merged
Merged
Conversation
Align example expo with SDK 57 expected range so WAIT_FOR_CI_SELF_TEST expo install --check passes on shared main tree.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #14 +/- ##
=========================================
Coverage 59.54% 59.54%
Complexity 15 15
=========================================
Files 22 22
Lines 1048 1048
Branches 239 239
=========================================
Hits 624 624
Misses 352 352
Partials 72 72
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
alexdukeinvertase
marked this pull request as ready for review
October 22, 2026 09:20
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.
Summary
Mike: this is shared example-app Expo drift on
main— CI’sexpo install --checkrejectsexpo@57.0.25vs expected~57.0.31. It blocks docs/README PRs the same way; it’s not a docs content issue.What changed
WAIT_FOR_CI_SELF_TEST/wait-for-ci.shExpo gate can pass.example/package.jsonexpo~57.0.25→~57.0.31expo install --checkyarn.lockexpo@57.0.31(+ related Expo tooling)Test plan / results
yarn workspace react-native-coverage-example exec expo install --check→ exit 0 (Dependencies are up to date)unitjob (incl. wait-for-ci Expo check) green on this PR