Repository navigation
chore: guard Babel and Expo status bar major updates - #422
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Oct 1, 2026
This branch was successfully deployed
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
1 participant
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.
Dependabot still proposes Babel 8 and expo-status-bar 57 upgrades after the React Native toolchain exclusions were added, as shown in #407 and #419. React Native 0.87.1 uses Babel 7, and the example does not include the Expo runtime required by newer expo-status-bar releases. This change excludes standalone major version updates for
@babel/*andexpo-status-barso those upgrades receive a compatibility review.Minor and patch updates stay enabled. The rules use version update types, so Dependabot can still propose security updates.