Page MenuHomePhabricator

Rename React Native patchfile to reflect upgrade
ClosedPublic

Authored by ashoat on Sep 25 2023, 6:08 AM.
Tags
None
Referenced Files
F3507017: D9284.id31397.diff
Fri, Dec 20, 7:03 PM
Unknown Object (File)
Sat, Nov 30, 2:58 AM
Unknown Object (File)
Nov 12 2024, 5:59 AM
Unknown Object (File)
Oct 31 2024, 1:27 PM
Unknown Object (File)
Oct 31 2024, 1:26 PM
Unknown Object (File)
Oct 31 2024, 1:26 PM
Unknown Object (File)
Oct 31 2024, 1:25 PM
Unknown Object (File)
Oct 1 2024, 5:29 PM
Subscribers

Details

Summary
Test Plan

yarn cleaninstall:

$ /Users/ashoat/src/comm/node_modules/.bin/patch-package
patch-package 6.4.7
Applying patches...
@expo/cli@0.4.11 ✔
@rainbow-me/rainbowkit@0.12.15 ✔
@react-native-clipboard/clipboard@1.11.1 ✔
hazel-server@5.1.1 ✔
olm@3.2.4 ✔
react-native@0.70.9 ✔
react-native-camera@3.31.0 ✔
react-native-ffmpeg@0.4.4 ✔
react-native-in-app-message@1.0.2 ✔
react-native-keyboard-input@6.0.1 ✔
react-native-orientation-locker@1.5.0 ✔
react-native-video@5.2.1 ✔
redux-persist@6.0.0 ✔
remote-redux-devtools@0.5.16 ✔
remotedev@0.2.9 ✔

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

So I actually tried to include this in D9227: https://phab.comm.dev/D9227?vs=on&id=31269#toc, but there was some additional stuff that got included when I ran patch package (figured that was safer than just renaming file)

c32dd2.png (946×1 px, 371 KB)

Was holding off on landing that diff until A. "Can you create a GitHub issue on the Expo repo and link it here before landing?" and B. trying to get rid of that (seemingly extraneous?) "hunk."

Looks like patch in this diff applies fine and CI continues to pass, so seems good to go?

This revision is now accepted and ready to land.Sep 25 2023, 11:27 AM