Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: pin react-native-tcp to hash (#12595)
## **Description** Fix it to the git commit hash we're using (yarn.lock resolved url tar.gz hash), instead of the latest commit on a contributor's pr branch on the fork (package.json) i.e. aprock/react-native-tcp@98fbc80 (note: [`master`](https://github.com/aprock/react-native-tcp/commits/master) is few commits ahead) note: our [`develop`](https://github.com/MetaMask/metamask-mobile/tree/develop) has two more such cases ([1](https://github.com/MetaMask/metamask-mobile/blob/develop/package.json#L169), [2](https://github.com/MetaMask/metamask-mobile/blob/develop/package.json#L209)) ## **Related issues** Fixes: variable commit hashes, if the lockfile were to be removed/regenerated ## **Manual testing steps** ## **Screenshots/Recordings** ### **Before** ### **After** ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.
- Loading branch information