build(deps): bump @metamask/eth-json-rpc-infura from 10.0.0 to 10.2.0

[dependabot]

Bumps @metamask/eth-json-rpc-infura from 10.0.0 to 10.2.0.

Release notes

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

10.2.0

Added

• Add sei-mainnet and sei-testnet as Infura supported network (#117)

10.1.1

Fixed

• Fix middleware so that non-standard JSON-RPC error responses are no longer treated as successful responses (#123)
  • A "non-standard" error response is one with an error field but where there are more properties in the error object than expected

10.1.0

Added

• Add a way to pass an RPC service to createInfuraMiddleware (#116)
  • The new, recommended function signature is now createInfuraMiddleware({ rpcService: AbstractRpcService; options?: { source?: string; headers?: HeadersInit } }), 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 dependencies to remove pre-11.x versions of @metamask/utils from dependency tree (#118)
  • Bump @metamask/eth-json-rpc-provider from ^4.1.5 to ^4.1.7
  • Bump @metamask/json-rpc-engine from ^10.0.0 to ^10.0.2
  • Bump @metamask/rpc-errors from ^7.0.0 to ^7.0.2
  • Bump @metamask/utils from ^9.1.0 to ^11.1.0

Deprecated

• Deprecate passing an RPC endpoint to createInfuraMiddleware (#116)
  • See recommended function signature above
  • The existing signature createInfuraMiddleware({ network?: InfuraJsonRpcSupportedNetwork; maxAttempts?: number; source?: string; projectId: string; headers?: Record<string, string>; }) will be removed in a future major version

Changelog

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

[10.2.0]

Added

• Add sei-mainnet and sei-testnet as Infura supported network (#117)

[10.1.1]

Fixed

• Fix middleware so that non-standard JSON-RPC error responses are no longer treated as successful responses (#123)
  • A "non-standard" error response is one with an error field but where there are more properties in the error object than expected

[10.1.0]

Added

• Add a way to pass an RPC service to createInfuraMiddleware (#116)
  • The new, recommended function signature is now createInfuraMiddleware({ rpcService: AbstractRpcService; options?: { source?: string; headers?: HeadersInit } }), 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 dependencies to remove pre-11.x versions of @metamask/utils from dependency tree (#118)
  • Bump @metamask/eth-json-rpc-provider from ^4.1.5 to ^4.1.7
  • Bump @metamask/json-rpc-engine from ^10.0.0 to ^10.0.2
  • Bump @metamask/rpc-errors from ^7.0.0 to ^7.0.2
  • Bump @metamask/utils from ^9.1.0 to ^11.1.0

Deprecated

• Deprecate passing an RPC endpoint to createInfuraMiddleware (#116)
  • See recommended function signature above
  • The existing signature createInfuraMiddleware({ network?: InfuraJsonRpcSupportedNetwork; maxAttempts?: number; source?: string; projectId: string; headers?: Record<string, string>; }) will be removed in a future major version

Commits

• 311dd47 10.2.0 (#125)
• bff7a3e feat: add SEI as new infura supported network (#117)
• f10fd06 10.1.1 (#124)
• e157880 chore: update security-code-scanner@main to action-security-code-scanner@v1 (...
• b3e773a Treat non-standard JSON-RPC errors as standard (#123)
• 0611543 chore: add workflow_dispatch to security-code-scanner (#121)
• 7f45fca 10.1.0 (#120)
• f24567d Allow createInfuraMiddleware to take an RPC service (#116)
• 12b2574 Bump all dependencies (#118)
• See full diff in compare view

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)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​metamask/​eth-json-rpc-infura@​10.0.0 ⏵ 10.2.0	+1		+1	+6

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Block		@metamask/[email protected] has Network access. Module: globalThis["fetch"] Location: Package overview From: yarn.lock → npm/@metamask/[email protected] ℹ Read more on: This package | This alert | What is network access? Next steps: 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 [email protected]. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report