-
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
chore(deps): force secp256k1 4.0.4 version with resolutions #28177
chore(deps): force secp256k1 4.0.4 version with resolutions #28177
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. |
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: npm/[email protected] |
Builds ready [8a67e17]
Page Load Metrics (2274 ± 218 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
8a67e17
to
2674d2d
Compare
Builds ready [2674d2d]
Page Load Metrics (2493 ± 363 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
Builds ready [13c075a]
Page Load Metrics (1908 ± 173 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
lavamoat/browserify/main/policy.json
Outdated
@@ -4273,22 +4273,6 @@ | |||
"TextEncoder": true | |||
} | |||
}, | |||
"eth-lattice-keyring>gridplus-sdk>secp256k1": { |
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.
this change indicates there's now one less version of the package.
This adds up with what we see in the lockfile too.
I can confirm you've successfully upgraded secp256k1 to 4.0.4 only.
package.json
Outdated
"secp256k1@npm:^4.0.0": "4.0.4", | ||
"secp256k1@npm:^4.0.1": "4.0.4", | ||
"secp256k1@npm:4.0.2": "4.0.4", | ||
"secp256k1@npm:4.0.3": "4.0.4" |
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.
It's a bit messy, but if it's not ending up in main branch later, it doesn't matter
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!
Cherry-picks #28145 to v12.5.1, and brings #28177 into v12.5.1 as well. The latter originally targeted v12.6.0, but we need it for a hotfix ahead of that. The PR description for that was: ## **Description** Forcing resolutions to fix `yarn audit` warnings and more specifically this issue: - GHSA-584q-6j8j-r5pm I decided to be very explicit about the resolution itself based on the output of: ```console $ yarn why secp256k1 ├─ ethereum-cryptography@npm:0.1.3 │ └─ secp256k1@npm:4.0.4 (via npm:^4.0.1) │ ├─ ganache@npm:7.9.2 │ └─ secp256k1@npm:4.0.3 (via npm:4.0.3) │ ├─ ganache@patch:ganache@npm%3A7.9.2#~/.yarn/patches/ganache-npm-7.9.2-a70dc8da34.patch::version=7.9.2&hash=7d7c66 │ └─ secp256k1@npm:4.0.3 (via npm:4.0.3) │ ├─ gridplus-sdk@npm:2.5.1 │ └─ secp256k1@npm:4.0.2 (via npm:4.0.2) │ └─ hdkey@npm:2.1.0 └─ secp256k1@npm:4.0.4 (via npm:^4.0.0) ``` We could also have a more straightforward resolution like: ```json ... "resolutions": { ... "secp256k1": "4.0.4" } ... ``` But that could also catch version with different major. Let me know what would be the preferred solution here. [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/28176?quickstart=1) ## **Related issues** Fixes: GHSA-584q-6j8j-r5pm ## **Manual testing steps** N/A ## **Screenshots/Recordings** ### **Before** ### **After** ## **Pre-merge author checklist** - [ ] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.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. --------- Co-authored-by: Charly Chevalier <[email protected]> Co-authored-by: sahar-fehri <[email protected]>
13c075a
to
3df0a16
Compare
Builds ready [3df0a16]
Page Load Metrics (1871 ± 118 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
Description
Forcing resolutions to fix
yarn audit
warnings and more specifically this issue:I decided to be very explicit about the resolution itself based on the output of:
We could also have a more straightforward resolution like:
But that could also catch version with different major.
Let me know what would be the preferred solution here.
Related issues
Fixes: GHSA-584q-6j8j-r5pm
Manual testing steps
N/A
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist