docs+ci: Expo plugin, v7 upgrade path, SECURITY.md, SHA-pinned Actions - #374
Merged
Conversation
Point new installs at latest v9 with New Architecture recommended. Keep ^7 only for React Native < 0.70, add a one-page v7 upgrade path, Expo install + expo-file-system examples, comparison vs JSZip/Nitro, empty-dir and FIFO notes, and fix stale playground paths. Co-authored-by: plrthink <plrthink@gmail.com>
Add app.plugin.js so Expo autolinking accepts plugins: ["react-native-zip-archive"], wire it in package.json, register it in playground-expo, and retarget the npm description/keywords toward Expo, EAS, password zip, and TurboModules. Co-authored-by: plrthink <plrthink@gmail.com>
Document 9.x as the active line, 8.x as upgrade-only, and 7.x as security-only through 2027-02-19. Zip Slip/symlink 7.x backports are explicitly not done yet. Co-authored-by: plrthink <plrthink@gmail.com>
Replace mutable @v4/@v2 tags with full commit SHAs so workflow resolutions cannot silently move. Co-authored-by: plrthink <plrthink@gmail.com>
Lock the growth-branch listing and plugin contract in Jest: Expo app.plugin.js is a no-op, npm pack includes it and SECURITY.md, and README/SECURITY claims still match the native helpers they describe. Co-authored-by: plrthink <plrthink@gmail.com>
GitHub API confirms each pin: checkout/setup-node v4.4.0, cache v4.3.0, setup-java v4.9.1, upload-artifact v4.6.2, android-emulator-runner v2.38.0. Co-authored-by: plrthink <plrthink@gmail.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Expo resolves config plugins via app.plugin.js at the package root, then package main — not an expo.plugin key. That key is dead metadata and a legacy app-config location, so remove it and assert the real resolution file is published instead. Co-authored-by: plrthink <plrthink@gmail.com>
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
2 participants
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
Ships the P0/P1/P2 growth work that does not need device hardware.
^7only for RN < 0.70Test plan
npm test(49)app.plugin.jsNot in this PR: RNZA-5 old-arch matrix, RNZA-6 Interop, RNZA-16, RNZA-20.