deps: @metamask/eth-hd-keyring@^6.0.0->^7.0.1

[legobeat]

Description

• deps: Bump @metamask/eth-hd-keyring from ^6.0.0 to ^7.0.1
  • diff
  • CHANGELOG

Changes

• Changed: Bump @metamask/eth-hd-keyring from ^6.0.0 to ^7.0.1

References

Resolves

• Update eth-hd-keyring to v7 #272

Blocking

• 14.0.0 #265

Related:

• Bump @metamask/eth-sig-util from 6.0.0 to 7.0.0 #269
• deps: @metamask/eth-simple-keyring@^5.0.0->^6.0.0 #273

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation for new or updated code as appropriate (note: this will usually be JSDoc)
• I've highlighted breaking changes using the "BREAKING" category above as appropriate

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@metamask/eth-hd-keyring	6.0.2...7.0.1	None	+0/-9	59.7 kB	metamaskbot

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

[legobeat]

@SocketSecurity ignore @metamask/eth-hd-keyring@7.0.1

[jiexi]

Unrelated. Looks like @ethereumjs/wallet 2.0.0 introduces a new @ethereumjs/util version

jiexi@1200775 ~/P/KeyringController ((013d97f1))> yarn why @ethereumjs/util
├─ @ethereumjs/common@npm:3.2.0
│ └─ @ethereumjs/util@npm:8.1.0 (via npm:^8.1.0)
│
├─ @ethereumjs/tx@npm:4.2.0
│ └─ @ethereumjs/util@npm:8.1.0 (via npm:^8.1.0)
│
├─ @ethereumjs/wallet@npm:2.0.0
│ └─ @ethereumjs/util@npm:9.0.0 [6d0b6] (via npm:^9.0.0 [6d0b6])
│
├─ @metamask/eth-hd-keyring@npm:7.0.1
│ └─ @ethereumjs/util@npm:8.1.0 (via npm:^8.1.0)
│
├─ @metamask/eth-sig-util@npm:5.1.0
│ └─ @ethereumjs/util@npm:8.1.0 (via npm:^8.0.6)
│
├─ @metamask/eth-sig-util@npm:7.0.0
│ └─ @ethereumjs/util@npm:8.1.0 (via npm:^8.1.0)
│
└─ @metamask/eth-simple-keyring@npm:5.0.0
└─ @ethereumjs/util@npm:8.1.0 (via npm:^8.0.0)

[legobeat]

Unrelated. Looks like @ethereumjs/wallet 2.0.0 introduces a new @ethereumjs/util version

jiexi@1200775 ~/P/KeyringController ((013d97f1))> yarn why @ethereumjs/util
├─ @ethereumjs/common@npm:3.2.0
│ └─ @ethereumjs/util@npm:8.1.0 (via npm:^8.1.0)
│
├─ @ethereumjs/tx@npm:4.2.0
│ └─ @ethereumjs/util@npm:8.1.0 (via npm:^8.1.0)
│
├─ @ethereumjs/wallet@npm:2.0.0
│ └─ @ethereumjs/util@npm:9.0.0 [6d0b6] (via npm:^9.0.0 [6d0b6])
│
├─ @metamask/eth-hd-keyring@npm:7.0.1
│ └─ @ethereumjs/util@npm:8.1.0 (via npm:^8.1.0)
│
├─ @metamask/eth-sig-util@npm:5.1.0
│ └─ @ethereumjs/util@npm:8.1.0 (via npm:^8.0.6)
│
├─ @metamask/eth-sig-util@npm:7.0.0
│ └─ @ethereumjs/util@npm:8.1.0 (via npm:^8.1.0)
│
└─ @metamask/eth-simple-keyring@npm:5.0.0
└─ @ethereumjs/util@npm:8.1.0 (via npm:^8.0.0)

This should OK since here it's a devDependency only used in tests, though the runtime version will eventually get here too after the same has first been done in eth-sig-util and the keyrings.

[legobeat]

@jiexi Rebased on main and resolved yarn.lock conflicts after merge of #273

[jiexi]

🚀