-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump @metamask/providers to v13.0.0 #20917
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 |
lavamoat/build-system/policy.json
Outdated
@@ -1136,6 +1136,21 @@ | |||
"string.prototype.matchall>side-channel": true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pretty sure we don't want to commit these changes? I believe these are OS specific.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Builds ready [806e33b]
Page Load Metrics (1045 ± 377 ms)
Bundle size diffs
|
Driven by a need to get rid of
window.ethereum.networkVersion
as a part of removing networkId work. This PR bumps@metamask/providers
from v11.1.0 to v13.0.0, which introduces a deprecation warning when accessingwindow.ethereum.networkVersion
(as well aschainId
andselectedAddress
). 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 alreadybrowserify
from v16.5.1 to v17.0.0 which is required for polyfillingstreams.pipeline
which is now used in@metamask/providers
MetaMask/providers@v11.1.0...v13.0.0
Explanation
Screenshots/Screencaps
Before
After
Manual Testing Steps
window.ethereum.chainId
window.ethereum.chainId
againwindow.ethereum.networkVersion
andwindow.ethereum.selectedAddress
Pre-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 Board
label.In this case, a QA Engineer approval will be be required.