metamask-mobile
metamask-mobile copied to clipboard
chore: Update json-rpc-provider & json-rpc-middleware & json-rpc-filters
Description
This PR is blocked due to breaking changes on the errors thrown to the dapps. More info in this thread
This PR includes:
Related issues
Fixes:
Manual testing steps
- Go to in-app browser
- Test connect with multiple dapps
- Perform transaciton on test dapp
Screenshots/Recordings
https://github.com/MetaMask/metamask-mobile/assets/46944231/c608d957-6684-40e2-8963-67a11dc610df
Before
After
Pre-merge author checklist
- [ ] I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using JSDoc format if applicable
- [ ] I’ve applied the right labels on the PR (see labeling guidelines). 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.
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
| Package | New capabilities | Transitives | Size | Publisher |
|---|---|---|---|---|
| npm/@metamask/[email protected] | None | 0 |
24.6 kB | lgbot |
| npm/@metamask/[email protected] | network | +4 |
462 kB | metamaskbot |
| npm/@metamask/[email protected] | None | 0 |
188 kB | metamaskbot |
🚮 Removed packages: npm/@metamask/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎
This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.
Bitrise
❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌
Commit hash: c6e47edecbb33ca933d7fa25965e7c8f81817f75 Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/5cd3b4ea-3953-4e13-b096-d6d52802d5ba
[!NOTE]
- You can kick off another
pr_smoke_e2e_pipelineon Bitrise by removing and re-applying theRun Smoke E2Elabel on the pull request
Bitrise
❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌
Commit hash: ddfb55d9b187e74463d74ddabf94764944ce86c9 Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/bbb6471d-e11b-4189-bd15-75232ee82fed
[!NOTE]
- You can kick off another
pr_smoke_e2e_pipelineon Bitrise by removing and re-applying theRun Smoke E2Elabel on the pull request
Bitrise
❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌
Commit hash: 49cf6fa10ded0c7f305ca078e45a23b88214b4ff Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d5bf5805-162b-4412-9712-f77192432d9d
[!NOTE]
- You can kick off another
pr_smoke_e2e_pipelineon Bitrise by removing and re-applying theRun Smoke E2Elabel on the pull request
Bitrise
✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅
Commit hash: 010a194c05c75c90cd96a6d569f62adac5d2b238 Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/36deec35-0dff-4470-a857-54329d86cdf0
[!NOTE]
- You can kick off another
pr_smoke_e2e_pipelineon Bitrise by removing and re-applying theRun Smoke E2Elabel on the pull request
Bitrise
❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌
Commit hash: b7b8f28bf0022cc94b4912dc191ae2d735ca0698 Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/34830c05-7d3b-42d3-b326-bc50fac8350a
[!NOTE]
- You can kick off another
pr_smoke_e2e_pipelineon Bitrise by removing and re-applying theRun Smoke E2Elabel on the pull request
Bitrise
✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅
Commit hash: 0debc0505a91d14bb9a9f9c6840555561310d340 Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f5aa28d3-d608-4e2e-a025-41dd07661ca6
[!NOTE]
- You can kick off another
pr_smoke_e2e_pipelineon Bitrise by removing and re-applying theRun Smoke E2Elabel on the pull request
Quality Gate passed
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
55.6% Coverage on New Code
0.0% Duplication on New Code
Codecov Report
Attention: Patch coverage is 71.42857% with 4 lines in your changes missing coverage. Please review.
Project coverage is 49.49%. Comparing base (
b013c71) to head (0debc05). Report is 122 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #10098 +/- ##
==========================================
+ Coverage 47.24% 49.49% +2.24%
==========================================
Files 1370 1427 +57
Lines 33304 34420 +1116
Branches 3586 3801 +215
==========================================
+ Hits 15736 17035 +1299
+ Misses 16607 16323 -284
- Partials 961 1062 +101
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Did a light check on SDK and it seems to be all good ✅
This PR has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 7 days. Thank you for your contributions.
This has been picked up in #11952