Update dependency @noble/secp256k1 to v2.2.2 - autoclosed #21
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/noble-secp256k1-2.x-lockfile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
2.1.0
->2.2.2
Release Notes
paulmillr/noble-secp256k1 (@noble/secp256k1)
v2.2.2
Compare Source
Full Changelog: https://github.com/paulmillr/noble-secp256k1/compare/2.2.1...2.2.2
v2.2.1
Compare Source
Same as 2.2.0, but now publishing to JSR without slow-types option.
Full Changelog: https://github.com/paulmillr/noble-secp256k1/compare/2.2.0...2.2.1
v2.2.0
Compare Source
What's Changed
opts.extraEntropy
when signingisolatedDeclarations
optionNew Contributors
Full Changelog: https://github.com/paulmillr/noble-secp256k1/compare/2.1.0...2.2.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
File name: yarn.lock
1c6304ca4b
to8968d8cba1
Update dependency @noble/secp256k1 to v2.2.1to Update dependency @noble/secp256k1 to v2.2.2Update dependency @noble/secp256k1 to v2.2.2to Update dependency @noble/secp256k1 to v2.2.2 - autoclosedPull request closed