Conversation
|
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. |
|
No top level dependency changes detected. Learn more about Socket for GitHub ↗︎ |
|
👍 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. |
|
@metamaskbot update-policies |
|
Policies updated |
|
@metamaskbot update-policies |
|
Policies updated |
Builds ready [9873ef8]
Page Load Metrics (1590 ± 57 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #20917 +/- ##
========================================
Coverage 68.63% 68.63%
========================================
Files 1017 1017
Lines 40790 40790
Branches 10896 10896
========================================
Hits 27996 27996
Misses 12794 12794 ☔ View full report in Codecov by Sentry. |
|
Can we only have one version of |
Resolved by #20946 . Thank you for taking care of that!
Looks like this may require some manual attention. I'll try to take a look today.
Hard to say. It's awkward because the provider is almost always used in the browser context, but not strictly. Because it's totally valid to be used in nodejs, I think this is a concern of metamask-extension and not providers. |
|
Current provider alignment status. Still have v11 floating around
bump provider to v13 in |
| @@ -1136,6 +1136,21 @@ | |||
| "string.prototype.matchall>side-channel": true | |||
There was a problem hiding this comment.
pretty sure we don't want to commit these changes? I believe these are OS specific.
There was a problem hiding this comment.
i believe this comes from the auto generated lavamoat policies
|
@metamaskbot update-policies |
|
Policies updated |
Builds ready [37f4f50]
Page Load Metrics (1324 ± 344 ms)
Bundle size diffs
|
|
No longer blocked by having to align snaps (provider v11) and this change |
Builds ready [806e33b]
Page Load Metrics (1045 ± 377 ms)
Bundle size diffs
|
Driven by a need to get rid of
window.ethereum.networkVersionas a part of removing networkId work. This PR bumps@metamask/providersfrom v11.1.0 to v13.0.0, which introduces a deprecation warning when accessingwindow.ethereum.networkVersion(as well aschainIdandselectedAddress). The goal is to get this into the wild, alert devs, and to finally remove these properties in the future.Additionally, this PR bumpsCompleted in a separate PR alreadybrowserifyfrom v16.5.1 to v17.0.0 which is required for polyfillingstreams.pipelinewhich is now used in@metamask/providersMetaMask/providers@v11.1.0...v13.0.0
Explanation
Screenshots/Screencaps
Before
After
Manual Testing Steps
window.ethereum.chainIdwindow.ethereum.chainIdagainwindow.ethereum.networkVersionandwindow.ethereum.selectedAddressPre-merge author checklist
Pre-merge reviewer checklist
If further QA is required (e.g. new feature, complex testing steps, large refactor), add the
Extension QA Boardlabel.In this case, a QA Engineer approval will be be required.