Upgrade noble and scure dependencies to v2.2#4588
Open
paulmillr wants to merge 1 commit into
Open
Conversation
|
@paulmillr is attempting to deploy a commit to the Wevm Team on Vercel. A member of the Team first needs to authorize it. |
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
commit: |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
See #4575. Feel free to copy / edit / incorporate into your own branch. Feel free to delay until v3 (this is compat-breaking because of node.js >=20.19 requirement) is released.
Duplicating text from 4575:
We now have stable noble v2.2.x.
Reason 1: The packages had undergone through a very detailed self-audit, which found more minor & medium-severity issues than all previous third party audits combined.
Reason 2: Because of the LLMs, attackers are having a breakthrough and it would be great to have Viem line up with the latest, and the only security-relevant noble versions. Older versions would degrade and probably get broken sooner.
hashes
curves