Repository navigation
fix(deps): update dependency @noble/hashes to v2 - #22
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/noble-hashes-2.x
branch
5 times, most recently
from
October 18, 2026 13:42
89e0f63 to
f5e81f3
Compare
renovate
Bot
force-pushed
the
renovate/noble-hashes-2.x
branch
4 times, most recently
from
October 22, 2026 04:38
8bcd8f7 to
dbb8252
Compare
renovate
Bot
force-pushed
the
renovate/noble-hashes-2.x
branch
from
October 27, 2026 00:59
dbb8252 to
b45d652
Compare
|
This branch has not been deployed
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.



This PR contains the following updates:
^1.8.0→^2.0.0Release Notes
paulmillr/noble-hashes (@noble/hashes)
v2.4.0Compare Source
Security and correctness
Misc
t: 3,m: 1024 ** 2KiB (1 GiB),p: 1,dkLen: 32, and a 1 GiBmaxmemlimit; larger-memory calls must setmaxmemexplicitly.maxmemto work forN: 2 ** 20,r: 8, andp: 1nextTickandasyncLoopnow yield throughscheduler.yield()when available orsetTimeoutotherwise, allowing timers, I/O, and rendering to progress. They also accept optional rejection cleanup; async Argon2, PBKDF2, and scrypt use it to wipe work state if scheduling is aborted.v2.3.0Compare Source
Performance
Other changes
HMAC._cloneIntoso it preservescanXOFin issue #134, reported by @ChALkeR, and corrected an Argon2d typo in issue #135.blake2.compressto the internal_compressmethod.v2.2.0Compare Source
dkLen=0handling inpbkdf2,blake2,turboshake, andkt.parallelHashwithblockLen=0.argon2progress callback reach 100%.digestIntoto return no value for better performance.dkLenvalues inargon2andblake2.Uint8Array, while TypeScript 5.9+ made it generic asUint8Array<ArrayBuffer>.TS2345.v2.0.1Compare Source
.jsextension for all module imports.@noble/hashes/sha3.@noble/hashes/sha3.js.package.jsonto support TypeScript autocompletion.maxmemerror message, contributed by @ChALkeR in pull request #121.v2.0.0Compare Source
High-level changes
.jsextension for all module imports.@noble/hashes/sha3.@noble/hashes/sha3.js.API changes
Uint8Arrayand prohibitedstringinputs.utils.utf8ToBytesto reproduce the previous behavior.sha256andsha512→sha2.js.blake2bandblake2s→blake2.js.ripemd160,sha1, andmd5→legacy.js._assert→utils.js.cryptomodule in favor of built-in WebCrypto.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.