chore(deps): force secp256k1 4.0.4 version with resolutions#28177
Merged
ccharly merged 0 commit intoVersion-v12.6.0from Oct 31, 2024
Merged
Conversation
Contributor
|
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/secp256k1@4.0.3 |
7 tasks
Collaborator
Builds ready [8a67e17]
Page Load Metrics (2274 ± 218 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
8a67e17 to
2674d2d
Compare
Collaborator
Builds ready [2674d2d]
Page Load Metrics (2493 ± 363 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
danjm
previously approved these changes
Oct 30, 2024
Collaborator
Builds ready [13c075a]
Page Load Metrics (1908 ± 173 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
naugtur
reviewed
Oct 30, 2024
lavamoat/browserify/main/policy.json
Outdated
| "TextEncoder": true | ||
| } | ||
| }, | ||
| "eth-lattice-keyring>gridplus-sdk>secp256k1": { |
Contributor
There was a problem hiding this comment.
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.
naugtur
reviewed
Oct 30, 2024
| "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" |
Contributor
There was a problem hiding this comment.
It's a bit messy, but if it's not ending up in main branch later, it doesn't matter
7 tasks
danjm
added a commit
that referenced
this pull request
Oct 31, 2024
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. [](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 <charly.chevalier@consensys.net> Co-authored-by: sahar-fehri <sahar.fehri@consensys.net>
13c075a to
3df0a16
Compare
Collaborator
Builds ready [3df0a16]
Page Load Metrics (1871 ± 118 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Forcing resolutions to fix
yarn auditwarnings 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