chore: update toruslabs/metadata-helper package#387
Open
Conversation
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
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.
Motivation and Context
Jira Link:
Description
How has this been tested?
Screenshots (if appropriate):
Types of changes
Checklist:
Note
Medium Risk
Updates a crypto-related dependency and adjusts MiMC sponge hashing to use the new
keccak256BytesAPI; any subtle hashing/output differences could change derived constants/keys. Remaining changes are lockfile churn from dependency resolution updates.Overview
Bumps
@toruslabs/metadata-helpersfrom^8.1.0to^8.2.0(root and Vue example), regeneratingpackage-lock.jsonfiles with updated transitive versions.Updates
src/subkey/mimcsponge.tsto usekeccak256Bytesinstead ofkeccak256, keepingkeccak256Paddedreturning the same hex string format viabytesToHex.Written by Cursor Bugbot for commit 20a6c6b. This will update automatically on new commits. Configure here.