Skip to content

chore(deps): bump @metamask/eth-json-rpc-middleware from 15.0.1 to 15.3.0 #497

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 25, 2025

Bumps @metamask/eth-json-rpc-middleware from 15.0.1 to 15.3.0.

Release notes

Sourced from @​metamask/eth-json-rpc-middleware's releases.

15.3.0

Added

  • Support EIP-5792 (#359)
    • Add support for RPC methods:
      • wallet_sendCalls
      • wallet_getCallsStatus
      • wallet_getCapabilities
    • Add optional hooks to WalletMiddlewareOptions:
      • getCapabilities
      • getTransactionReceiptsByBatchId
      • processSendCalls
    • Add types:
      • GetCallsStatusParams
      • GetCallsStatusReceipt
      • GetCallsStatusResult
      • GetCapabilitiesHook
      • GetCapabilitiesParams
      • GetCapabilitiesResult
      • GetTransactionReceiptsByBatchIdHook
      • ProcessSendCallsHook
      • SendCalls
      • SendCallsParams

15.2.0

Added

  • Add a way to pass an RPC service to createFetchMiddleware (#357)
    • The new, recommended function signature is now createFetchMiddleware({ rpcService: AbstractRpcService; options?: { originHttpHeaderKey?: string; } }), where AbstractRpcService matches the same interface from @metamask/network-controller
    • This allows us to support automatic failover to a secondary node when the network goes down

Changed

  • Bump @metamask/utils to ^11.1.0 (#358)

Deprecated

  • Deprecate passing an RPC endpoint to createFetchMiddleware (#357)
    • See recommended function signature above
    • The existing signature createFetchMiddleware({ btoa: typeof btoa; fetch: typeof fetch; rpcUrl: string; originHttpHeaderKey?: string; }) will be removed in a future major version
  • Deprecate PayloadWithOrigin type (#357)
    • There is no replacement for this type; it will be removed in a future major version.

15.1.2

Changed

  • Fix validation of primary type for signTypedDataV3 and signTypedDataV4 (#353)
    • It was updated to handle undefined input

15.1.1

Changed

  • Bump @metamask/eth-block-tracker from ^11.0.3 to ^11.0.4 (#351)
  • Bump @metamask/eth-json-rpc-provider from ^4.1.5 to ^4.1.7 (#351)
  • Bump @metamask/eth-sig-util from ^7.0.3 to ^8.1.2 (#351)
  • Bump @metamask/json-rpc-engine from ^10.0.0 to ^10.0.2 (#351)

... (truncated)

Changelog

Sourced from @​metamask/eth-json-rpc-middleware's changelog.

[15.3.0]

Added

  • Support EIP-5792 (#357)
    • Add support for RPC methods:
      • wallet_sendCalls
      • wallet_getCallsStatus
      • wallet_getCapabilities
    • Add optional hooks to WalletMiddlewareOptions:
      • getCapabilities
      • getTransactionReceiptsByBatchId
      • processSendCalls
    • Add types:
      • GetCallsStatusParams
      • GetCallsStatusReceipt
      • GetCallsStatusResult
      • GetCapabilitiesHook
      • GetCapabilitiesParams
      • GetCapabilitiesResult
      • GetTransactionReceiptsByBatchIdHook
      • ProcessSendCallsHook
      • SendCalls
      • SendCallsParams

[15.2.0]

Added

  • Add a way to pass an RPC service to createFetchMiddleware (#357)
    • The new, recommended function signature is now createFetchMiddleware({ rpcService: AbstractRpcService; options?: { originHttpHeaderKey?: string; } }), where AbstractRpcService matches the same interface from @metamask/network-controller
    • This allows us to support automatic failover to a secondary node when the network goes down

Changed

  • Bump @metamask/utils to ^11.1.0 (#358)

Deprecated

  • Deprecate passing an RPC endpoint to createFetchMiddleware (#357)
    • See recommended function signature above
    • The existing signature createFetchMiddleware({ btoa: typeof btoa; fetch: typeof fetch; rpcUrl: string; originHttpHeaderKey?: string; }) will be removed in a future major version
  • Deprecate PayloadWithOrigin type (#357)
    • There is no replacement for this type; it will be removed in a future major version.

[15.1.2]

Changed

  • Fix validation of primary type for signTypedDataV3 and signTypedDataV4 (#353)
    • It was updated to handle undefined input

[15.1.1]

Changed

  • Bump @metamask/eth-block-tracker from ^11.0.3 to ^11.0.4 (#351)
  • Bump @metamask/eth-json-rpc-provider from ^4.1.5 to ^4.1.7 (#351)
  • Bump @metamask/eth-sig-util from ^7.0.3 to ^8.1.2 (#351)
  • Bump @metamask/json-rpc-engine from ^10.0.0 to ^10.0.2 (#351)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot requested a review from a team as a code owner February 25, 2025 06:47
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 25, 2025
Copy link

socket-security bot commented Feb 25, 2025

New and updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@metamask/[email protected]3.0.0 None 0 202 kB metamaskbot
npm/@metamask/[email protected]15.3.0 None +5 1.47 MB gudahtt
npm/@metamask/[email protected]8.2.0 None 0 144 kB danfinlay, gudahtt, kumavis, ...6 more

View full report↗︎

Copy link

socket-security bot commented Feb 25, 2025

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
New author npm/@metamask/[email protected] 🚫
Unstable ownership npm/@metamask/[email protected] 🚫

View full report↗︎

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

What is unstable ownership?

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/main/metamask/eth-json-rpc-middleware-15.3.0 branch 2 times, most recently from 2e014d3 to 19a7822 Compare March 5, 2025 16:13
Bumps [@metamask/eth-json-rpc-middleware](https://github.com/MetaMask/eth-json-rpc-middleware) from 15.0.1 to 15.3.0.
- [Release notes](https://github.com/MetaMask/eth-json-rpc-middleware/releases)
- [Changelog](https://github.com/MetaMask/eth-json-rpc-middleware/blob/main/CHANGELOG.md)
- [Commits](MetaMask/eth-json-rpc-middleware@v15.0.1...v15.3.0)

---
updated-dependencies:
- dependency-name: "@metamask/eth-json-rpc-middleware"
  dependency-type: indirect
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/main/metamask/eth-json-rpc-middleware-15.3.0 branch from 19a7822 to 7f2e856 Compare March 17, 2025 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants