fix: upgrade bn.js to 4.12.3/5.2.3#1631
Merged
ShubhamChaturvedi7 merged 1 commit intomasterfrom Mar 2, 2026
Merged
Conversation
texastony
approved these changes
Feb 25, 2026
Contributor
texastony
left a comment
texastony
left a comment
There was a problem hiding this comment.
Changes LGTM.
Additionally, I searched the package-lock.json for "bn.js": "^4 and confirmed all hits were 4.12.3 or 5 something.
|
Hi, is there anything preventing this PR being merged and released? We're keen to get this bumped if not 🙂 |
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
3 participants
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.
Issue #, if available:
#1630
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Check any applicable: