Skip to content
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

[Snyk] Upgrade @metamask/providers from 10.2.1 to 16.1.0 #19

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

Conversation

OKEAMAH
Copy link
Owner

@OKEAMAH OKEAMAH commented Jun 7, 2024

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade @metamask/providers from 10.2.1 to 16.1.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 13 versions ahead of your current version.

  • The recommended version was released on a month ago.

Release notes
Package name: @metamask/providers
  • 16.1.0 - 2024-05-01

    Added

    • Restore deprecated properties, networkChanged event, and offline send() net_version support (#312)
    • Bump MetaMask dependencies (#310)
    • Bump @ metamask/safe-event-emitter from 3.0.0 to 3.1.1 (#309)
    • Bump @ metamask/utils from 8.3.0 to 8.4.0 (#311)
    • Bump tar from 6.1.13 to 6.2.1 (#314)
  • 16.0.0 - 2024-03-13

    Removed

    • BREAKING: Remove deprecated properties, networkChanged event, and offline send() net_version support (#306)
      • window.ethereum.chainId has been removed. Use the 'eth_chainId' RPC method instead.
      • window.ethereum.networkVersion has been removed. Use the 'net_version' RPC method instead.
      • window.ethereum.selectedAddress has been removed. Use the 'eth_accounts' RPC method instead.
      • networkChanged event has been removed. The closest equivalent is the chainChanged event.
      • window.ethereum.send() no longer resolves net_version offline (from cache).

    Changed

    • Bump @ metamask/json-rpc-engine from 7.3.2 to 7.3.3 (#305)
  • 15.0.0 - 2024-02-28

    Added

    • BREAKING: Add ESM build (#296)
      • It's no longer possible to import files from the dist folder directly, with the exception of ./dist/StreamProvider

    Changed

    • Bump several MetaMask dependencies (#304)
    • Export RequestArguments and ConsoleLike types (#302)
  • 14.0.2 - 2023-11-22

    Fixed

    • Don't send null params to underlying provider (#292)
  • 14.0.1 - 2023-11-16

    Fixed

    • Don't send undefined params to underlying provider (#290)
  • 14.0.0 - 2023-11-07

    Changed

    • BREAKING: Update to streams3 API (#288)
      • Update extension-port-stream from ^2.1.1 to ^3.0.0
        • Force subdependency readable-stream to ^3.6.2 in resolutions
      • Update json-rpc-middleware-stream from ^4.2.3 to ^5.0.1
      • Update @ metamask/object-multiplex from ^1.3.0 to ^2.0.0
      • Add direct dependency on readable-stream@^3.6.2
      • Replace internal usage of stream with readable-stream
  • 13.1.0 - 2023-10-11

    Added

    • Add support for EIP-6963 (#263)
      • initializeProvider() params object now accepts an optional providerInfo property with a value of EIP6963ProviderInfo object
      • Add eip6963AnnounceProvider() which supports a wallet by announcing a provider through the eip6963:announceProvider event and re-announcing the provider whenever an eip6963:requestProvider event is received
      • Add eip6963RequestProvider() which supports a dapp by dispatching an eip6963:requestProvider event and invoking a callback for each eip6963:announceProvider event received
      • Add EIP6963AnnounceProviderEvent type
      • Add EIP6963ProviderDetail type
      • Add EIP6963ProviderInfo type
      • Add EIP6963RequestProviderEvent type
  • 13.0.0 - 2023-09-15

    Changed

    • BREAKING: Update chainId, networkVersion, and selectedAddress to be read-only (#280)
    • Log deprecation warning when accessing chainId, networkVersion, and selectedAddress (#280)
    • Remove pump (#281)
  • 12.0.0 - 2023-09-05

    Changed

    • BREAKING: Replace eth-rpc-errors@^4.0.2 with @ metamask/rpc-errors@6.0.0 (#277)
    • BREAKING: Replace json-rpc-engine@^6.1.0 with @ metamask/json-rpc-engine@7.1.1 (#277)
    • Upgrade @ metamask/utils from ^6.2.0 to ^8.1.0 (#277)
  • 11.1.2 - 2023-09-04

    Changed

    • Update extension-port-stream to ^2.1.1 (#273)
  • 11.1.1 - 2023-08-04
  • 11.1.0 - 2023-06-26
  • 11.0.0 - 2023-05-11
  • 10.2.1 - 2022-11-17
from @metamask/providers GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @metamask/providers from 10.2.1 to 16.1.0.

See this package in npm:
@metamask/providers

See this project in Snyk:
https://app.snyk.io/org/okeamah/project/55482140-c34b-4694-b0f6-4318189c8771?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants