Repository navigation
Update Expo patches and fix Forge security findings - #9
Merged
Merged
Conversation
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.
Main CI fails because Expo Doctor now requires newer SDK 58 patches and the dependency audit reports four advisories against node-forge 1.4.2. Align the six Expo packages with the current SDK recommendation and pin node-forge 1.4.3, which fixes the reported advisories.
Preserve the Config, Metro and SecureStore patches on the updated packages. SecureStore's native bridge and policy inputs are unchanged; the patch bytes are identical and its package/provenance pins are refreshed. Retire the unused glob/path-scurry overrides after Expo removed those dependencies, and exercise its replacement project/template discovery APIs in the compatibility tests.
Refresh both production JS notice inventories from source maps and the Android inventory from resolved archives. SQLite's new native artifact retains the recorded source ID and identical vendored source/notice ranges. All existing notice guards remain active.
Validation:
Production signing and standalone device acceptance remain pending. After merge and green main CI, start a fresh manual Android release run.
Hosted CI run 43141182058 has passed quality, shared behavior, both exports and all seven labs. Runtime and native build jobs are still running.